-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
patch to load_changeset to also load has_many -> through changes #22
base: master
Are you sure you want to change the base?
patch to load_changeset to also load has_many -> through changes #22
Conversation
e6aaa17
to
3d2014d
Compare
I think it is likely desirable that we would sometimes want to call the default |
What about doing something similar to how |
Sure |
@punkisdead could you please add some documentation for this as well? |
Yes, absolutely. I've got a few other tasks that are taking priority right now, but will get back to it in a day or two. |
e58fba3
to
aa1e4e4
Compare
@punkisdead I saw you made some changes and updated the documentation Please advise once you are done. Do you still intend to add the other relationship functionality? |
I hadn't intended to add the other relationship functionality in this PR, selfishly our needs were only for this. I can possibly look into adding them later in a separate PR if you'd like. |
It would be sweet if we could add them within this PR. If you don't get around to it, I will try and take a look at some point. |
Ok, let me see what I can do. |
I would love this feature. I dont really need to reify anything but would love to be able to diff including the has_many associations |
+1 for this feature. Just tried it on paper_trail 15.1 and got the following error:
|
I had a need to try to track changes of a has many through relationship using paper trail and have leveraged some of the work in this project to do so. I'd like to start a conversation about how to best accomplish this, and also add the functionality to the other association types
has_many
,has_one
, etc.Below is the start of this work, and it is working for what our case needs, but still needs better testing and some refactoring yet.