-
Notifications
You must be signed in to change notification settings - Fork 7
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
Problem with Axiom and ActiveSupport #8
Comments
Issue also occurs with:
|
I blame activesupport doing core extensions in an incompatible way, again. Virtus and axiom both dont do core extensions. I'm also sick of workarounding broken core extensions in AS. But I'm not the maintainer of virtus, so I strongly suggest pusing that issue upstream to AS. |
Ok, so currently I will 'monkey patch' active_support method with |
While active_support does some things that we find questionable, I'm not sure this is one of them. It's expecting that all I'm going to think about this a bit, and see if there are fixes I can make on my end. |
@swistaczek I just pushed a commit to the repo that I believe should fix this. Can you test it out and let me know if it resolves your issue? If it does I'll release a new axiom-types gem and see if virtus' dep can be bumped too. |
Ok, thanks. I will take a look. |
Hello,
During 'grape' gem integration (rack API framework) and Mongoid I encountered an issue with ActiveSupport and Axiom.
Final stacktrace occurs while calling Class that is including Mongoid::Document.
I have examined that there is problem with class Axiom::Types::Infinity. That class can not be compared to other classes (done by ActiveSupport in subclasses.rb)
Excerpt from subclasses.rb:
Are we able to make Axiom::Types::Infinity comparable?
The text was updated successfully, but these errors were encountered: