You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of our applications is a non rails application and we use standalone activerecord 4.2.7.1, active_model_serializers 0.8.3 and ruby 2.3.1.
We are looking forward to update active_model_serializers to 0.10.x, but in this version railties is not an optional dependency anymore, and because of that it would mess our initialization.
Is there a reason behind this mandatory dependency? Is there a plan to make it work in a standalone manner as before?
Environment
ActiveModelSerializers Version (commit ref if not on tag): 0.10.2
Expected behavior vs actual behavior
One of our applications is a non rails application and we use standalone activerecord 4.2.7.1, active_model_serializers 0.8.3 and ruby 2.3.1.
We are looking forward to update active_model_serializers to 0.10.x, but in this version railties is not an optional dependency anymore, and because of that it would mess our initialization.
Is there a reason behind this mandatory dependency? Is there a plan to make it work in a standalone manner as before?
Environment
ActiveModelSerializers Version (commit ref if not on tag): 0.10.2
Output of
ruby -e "puts RUBY_DESCRIPTION"
: ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]OS Type & Version: OSX 10.11.6
Integrated application and version (e.g., Rails, Grape, etc):
Grape 0.17.0
Activerecord 4.2.7.1
The text was updated successfully, but these errors were encountered: