Skip to content
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

Railties dependency #1921

Closed
ggpasqualino opened this issue Sep 8, 2016 · 0 comments
Closed

Railties dependency #1921

ggpasqualino opened this issue Sep 8, 2016 · 0 comments

Comments

@ggpasqualino
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant