Closed latortuga closed 1 year ago
I just made the test because I am not sure how to fix this at this point and wanted y'all to know it was happening. I'm not entirely sure if this can be fixed because it seems to be regarding an argument to delegate that is determined dynamically but even if we can't make it function I figured it should not throw an error.
(btw @mislav thank you for will_paginate ❤️ )
Thank you for reporting!
The ruby 2.2 CI failure is not related to this change: https://github.com/ruby/setup-ruby/issues/496
I updated to 1.0 today because I saw the announcement in Ruby Weekly last week. I am now getting a NoMethodError where previously there was no error when parsing (on v.0.9.1):
To be clear, I can still use it but this particular construction seems to throw the parser.
I've made a minimal test case that recreates the behavior.