-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Fix #1571] - Do not write to ActiveModel::Dirty changes when assigning ... #1635
Conversation
2f1d7cb
to
79dc62e
Compare
@bensie @plribeiro3000 can you take a look at this please? |
I believe this is a safe change. I might be missing something but its a really simple change. 👍 |
👍 |
Change looks useful, but I think this line is not 'easy readable': |
@rusikf I can't think of a better way than |
I agree @eavgerinos this is fine as-is. |
Will merge it tomorrow after giving it a last crash-test. ^_^ |
|
||
context "and the previous value was an empty string" do | ||
before do | ||
@event.image = "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps you can this guy above to a before block inside the context when empty string is assigned
and get a little dry. What do you think?
…ng something blank to a mounter that was originally blank
[Fix #1571] - Do not write to ActiveModel::Dirty changes when assigning ...
...something blank to a mounter that was originally blank
This is a WIP. I'm not sure it doesn't break anything yet and want to experiment with it before merging.
Feedback is more than welcome