-
Notifications
You must be signed in to change notification settings - Fork 19
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
Getting NoMethodError after adding 'mongoid_includes' to Gemfile #9
Comments
@mityakoval Haven't tested the gem with mongoid 6. If you make a PR to add mongoid 6 to the test matrix I can take a look at the failing tests 😃 |
Ah, okay. I just saw #3 as successfully closed and assumed it already supports mongoid 6. 😃 |
Completely forgot about that PR 😅 I ran tests with I'm not able to take a look at this at the moment, but will happily accept any patch for what seems to be breaking changes in |
Very likely that it's related to mongodb/mongoid#4326, since in order to get the job done we need to modify some of Mongoid's internals, since it's not designed with extensibility in mind. |
@mityakoval v2.0.0 is now available, thanks again for the bug report! |
…and rails 4 can benefit
@ElMassimo We're also experiencing this with mongoid 5.2.0/mongoid_includes 1.1.3. Any chance of a backport to the 1.1 series? |
Happy to release a new version, but don't have time to check it until next week. In the meantime, could you try forking |
@ElMassimo The issue still exists with mongoid 5.1.6 and mongoid_includes 1.1.3. We cannot currently go back to mongoid 5.0 |
I meant to downgrade the gemspec requirement of this gem in your own fork. If you don't want to fork this repo, you could try using this in your Gemfile: gem 'mongoid_includes', git: '[email protected]:ElMassimo/mongoid_includes.git', ref: '05c8d0d409cdc17ca47e8e5cfa04546be47d91f9' |
Hello,
I'm getting
NoMethodError: undefined method 'first' for false:FalseClass
every time I query for any document. Once I remove this gem from the Gemfile everything works.The whole stack:
The text was updated successfully, but these errors were encountered: