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

Update non_field_errors object to follow spec #123

Merged
merged 2 commits into from
Jul 28, 2015

Conversation

jpadilla
Copy link
Contributor

Went ahead and worked on fixing #113 based on the previous discussion.

@jpadilla jpadilla mentioned this pull request Jul 28, 2015
@dustinfarris
Copy link
Owner

This looks good. Going to try it out before merging.

/cc @holandes22

});
} else {
out.push({
source: { pointer: `data/attributes/${key}`},
source: { pointer: `data/attributes/${key}` },
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ember Data 1.13.7 (released yesterday) "fixed" the pointer format to align with the JSON API spec.

emberjs/data#3558

I think you'll need to add a forward slash to the beginning here (and on line 125), and update the documentation to show compatibility with ED >= 1.13.7

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dustinfarris yeah you're right about that. Update coming up in a few minutes.

@jpadilla
Copy link
Contributor Author

@dustinfarris updated for ember-data 1.13.7

@dustinfarris
Copy link
Owner

This is working, but ED doesn't seem to do anything with the /data errors. Going to merge this and open an issue there.

dustinfarris added a commit that referenced this pull request Jul 28, 2015
Update non_field_errors object to follow spec
@dustinfarris dustinfarris merged commit 89cd919 into dustinfarris:master Jul 28, 2015
@dustinfarris
Copy link
Owner

Opened emberjs/data#3602

@jpadilla
Copy link
Contributor Author

@dustinfarris awesome, thanks. Subscribed over to that issue for any follow up.

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 this pull request may close these issues.

2 participants