-
Notifications
You must be signed in to change notification settings - Fork 62
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
[Meta Issue] Deprecating in favour of official Ember Data adapter #86
Comments
I've written down some steps that I think should be sufficient to transition to the new built-in JSON-API adapter/serializer:
Please let me know if there's anything else I can do to help. I'm also available on Slack during most of the day, CET. |
This is awesome! Thanks @wecc for your hard work. |
@wecc Thanks for the feedback. Let me know when docs to the new Serializer API is available. |
JSON API v1.0 compliance has been added in #82. |
I'm thinking maybe we should just go ahead and deprecate the library. I really want to move the code over to the latest Ember Data in the 1.13.x releases, but I just haven't had the time. @kurko would this be agreeable to you as well? |
Yes. I also don't think it's worth our time and effort to move in parallel with ED. |
This issue is closed by #89, we are now officially deprecated! |
The Ember Data team has decided to support JSON API out of the box in the upcoming v1.0 release. Given these developments we have decided to deprecate this library and move our users to the official Ember Data solution.
This issue is to keep track of other issues related to this topic. But should also serve as a place to discuss what we can do to make the migration as smooth as possible.
Extend DS.JSONAPIAdapter and DS.JSONAPISerializerRemove any code from adapter and serializer that is duped in the Ember Data oneAdd a deprecation notice to the Bower packageThe text was updated successfully, but these errors were encountered: