Skip to content

Don't require JSONAPISerializer #3

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

Open
ef4 opened this issue Aug 11, 2016 · 2 comments
Open

Don't require JSONAPISerializer #3

ef4 opened this issue Aug 11, 2016 · 2 comments

Comments

@ef4
Copy link
Contributor

ef4 commented Aug 11, 2016

We shouldn't make assumptions about the serialization format. (See PR #2).

The problem right now is that we serialize each record by itself and then use our own logic to combine them. Instead we could either use whatever ember-data uses for serializing entire collections, or stick with separate serialized models but do a separate pushPayload for each.

@davidpett
Copy link

Is there any progress on this? I see two open PRs that haven't been touched for a few months, checking to see how I can help.

@adentranter
Copy link

Currently using ember, ember data, ember fastboot using JSONSerializer.

Is there a better way to get the data rendered server side or is issue still going to the best way?

Im happy to write code this up if so.

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

Successfully merging a pull request may close this issue.

3 participants