-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
JSONAPI adapter content-type is being blanked over by application/vnd.api+json on POST #6167
Comments
I've put a project showing simple program to reproduce the issue: The application route has CreateRecord in it. It will use the plan adapter (as proven by the alert("Called this"); appearing in the application route). It makes this request in chrome. I can see the x-access-token there look, but the content-type is not set.
|
@Benjy1979 if you properly case to |
No it stays the same |
I think this will resolve it: #6169 |
How do I get hold of the changes, I'm not too familiar with what I can do with that link. 1 of the tests are failing. I normally just use ember-cli-update |
@snewcomer was this fixed by #6341 ? |
Yes it was! At least for the For |
Ah yes it is working now, my extended adapter for a particular model is reading the header callback and the request has the specified one in the request. Thrilled, and thanks very much. |
Reproduction
Please provide one of the following:
A what?
observe the unexpected result.
Not familiar with it. It doesn't let me add an adapter and does not have the right version in the dropdown.
Here is a repository
Check POST in the model adapters of CreateRecord call.
Description
See this for description
Versions
Run the following command and paste the output below:
npm ls ember-source && npm ls ember-cli && npm ls ember-data
.P.S. If any of the packages show more than one installed version, that may be the root cause of the issue!
Thanks again!
The
ember-data
Team <3The text was updated successfully, but these errors were encountered: