Skip to content
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

Compatability with Rails 5.2's ActiveModel::Dirty #19

Merged
merged 9 commits into from
Dec 20, 2018

Conversation

benlangfeld
Copy link
Contributor

  • We're now expected to call #reset_changes, rather than manipulating @changed_attributes directly.
  • ActiveRecord::Dirty now assumes that any object it's included in which has an @attributes instance variable is database-backed, and has very specific API requirements for @attributes (must be an array of ActiveModel::Attribute instances). This conflicts with modis' @attributes, so we trivially renamed this to @modis_attributes to distinguish them.

jruby could not install this development dependency. And that is all it is, stackprof is a call-stack profiler. Not crucial to successful builds and can be added again by someone who may intend to use it.
@benlangfeld
Copy link
Contributor Author

I'd suggest merging #18 prior to this (and rebasing it), and closing #16 in favour of this.

* We're now expected to call `#reset_changes`, rather than manipulating `@changed_attributes` directly.
* `ActiveRecord::Dirty` now assumes that any object it's included in which has an `@attributes` instance variable is database-backed, and has very specific API requirements for `@attributes` (must be an array of  `ActiveModel::Attribute` instances). This conflicts with modis' `@attributes`, so we trivially renamed this to `@modis_attributes` to distinguish them.
@benlangfeld
Copy link
Contributor Author

I incorporated #18, along with my suggestion for support (only actively supported Ruby and Rails versions) into this PR for ease of merging.

Copy link
Collaborator

@garettarrowood garettarrowood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@garettarrowood
Copy link
Collaborator

@ileitch @Tonkpils - I will merge this in a few hours unless I hear otherwise from one of you. However, I am not an owner and will now be able to cut a new release with the upgrade. A 3.0 release seems most appropriate. Could you add me as an owner?

Otherwise, perhaps @aried3r , who looks to have push rights, can assist? I believe this change will make rpush Rails 5.2 compatible as well.

@ileitch
Copy link
Member

ileitch commented Dec 20, 2018

@garettarrowood I'll add you, what's your rubygems.org email address?

@garettarrowood
Copy link
Collaborator

It's garettarrowood@gmail.com . Thanks @ileitch !

@ileitch
Copy link
Member

ileitch commented Dec 20, 2018

@garettarrowood Done 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants