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

Release 5.9 backports #1083

Merged
merged 2 commits into from
Feb 18, 2015
Merged

Release 5.9 backports #1083

merged 2 commits into from
Feb 18, 2015

Conversation

cbeer
Copy link
Member

@cbeer cbeer commented Feb 17, 2015

I think we should backport these fixes to a 5.9.3 release.

…not deep-dup'ed to preserve the original classes

Fixes #1061

If those class names are dup'ed, methods that expect ActiveModel::Naming don't
behave correctly
@jcoyne
Copy link
Member

jcoyne commented Feb 17, 2015

Yes, good idea.

cbeer added a commit that referenced this pull request Feb 18, 2015
@cbeer cbeer merged commit 51172f0 into release-5.9 Feb 18, 2015
@cbeer cbeer deleted the release-5.9-backports branch February 18, 2015 02:13
alias_method :inheritable_copy, :deep_dup
##
# Rails 4.x provides `#deep_dup`, but it aggressively `#dup`'s class names
# too. These model names should not be `#dup`'ed or we might break ActiveModel::Naming.
Copy link
Member

Choose a reason for hiding this comment

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

thanks for the comment, I get it now. Those aren't class names, technically, those are classes themselves, where dup'ing would make a new class.

@cbeer cbeer modified the milestone: 5.9.3 Feb 21, 2015
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.

3 participants