We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Ruby 2.6.0 was released this week, and introduces Enumerator::Chain and Enumerable#filter.
2.6.0
The filterer gem already implements the chain and filter methods on an ActiveRecord collection.
filterer
chain
filter
On older rubies (<2.6) everything works fine;
# Ruby 2.5.x > User.where('1=1').chain => [#<User:0x00007fe8bbf5f9c3 ... etc as expected.
However, on new rubies (>2.6.0) we see the following problem;
# Ruby 2.6.0 > User.where('1=1').chain => #<Enumerator::Chain: ...>
It seems the simplest solution is to rename or avoid the .chain and .filter methods in this gem.
.chain
.filter
Thoughts?
The text was updated successfully, but these errors were encountered:
In my PR (aptly numbered #26), I've worked around this Ruby 2.6 conflict with the following method renames;
filter -> filterer chain -> filterer_chain
Sorry, something went wrong.
@olliebennett looks like you have the active fork. @ajb what are the chances of getting him as a maintainer or at least with access?
No branches or pull requests
Ruby
2.6.0
was released this week, and introduces Enumerator::Chain and Enumerable#filter.The
filterer
gem already implements thechain
andfilter
methods on an ActiveRecord collection.On older rubies (<2.6) everything works fine;
However, on new rubies (>2.6.0) we see the following problem;
It seems the simplest solution is to rename or avoid the
.chain
and.filter
methods in this gem.Thoughts?
The text was updated successfully, but these errors were encountered: