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

5-0-stable: Fix unscoping default_scope in STI associations #30267

Merged
merged 2 commits into from
Aug 15, 2017

Conversation

kamipo
Copy link
Member

@kamipo kamipo commented Aug 15, 2017

Backported #29834.

Since 5c71000, it has lost to be able to unscope default_scope in STI
associations. This change will use .empty_scope? instead of
.values.empty? to regard as an empty scope if only have
type_condition.

Since 5c71000, it has lost to be able to unscope `default_scope` in STI
associations. This change will use `.empty_scope?` instead of
`.values.empty?` to regard as an empty scope if only have
`type_condition`.
@rails-bot
Copy link

warning Warning warning

  • Pull requests are usually filed against the master branch for this repo, but this one is against 5-0-stable. Please double check that you specified the right target!

@rafaelfranca rafaelfranca merged commit d84123e into 5-0-stable Aug 15, 2017
@rafaelfranca rafaelfranca deleted the backport_29834 branch August 15, 2017 19:51
matthewd pushed a commit to matthewd/rails that referenced this pull request Dec 20, 2017
5-0-stable: Fix unscoping `default_scope` in STI associations
matthewd pushed a commit to matthewd/rails that referenced this pull request Dec 20, 2017
5-0-stable: Fix unscoping `default_scope` in STI associations
matthewd pushed a commit to matthewd/rails that referenced this pull request Dec 20, 2017
5-0-stable: Fix unscoping `default_scope` in STI associations
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