Skip to content

Use 204 on empty delete response #48

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

Merged
merged 2 commits into from
Mar 13, 2017
Merged

Use 204 on empty delete response #48

merged 2 commits into from
Mar 13, 2017

Conversation

medokin
Copy link
Contributor

@medokin medokin commented Mar 13, 2017

@medokin
Copy link
Contributor Author

medokin commented Mar 13, 2017

No idea why the test is failing

@jaredcnance
Copy link
Contributor

@medokin thanks for the PR! I'll dig into it this afternoon.

this check was happening on the wrong test
@jaredcnance
Copy link
Contributor

the test you updated was intended to verify that the server returns a 404 if a DELETE request is received for an entity that doesn't exist. I've updated the appropriate tests.

Currently, the organization of the tests is less than desirable and I hope to change that in the near future

@jaredcnance jaredcnance merged commit d82db99 into json-api-dotnet:master Mar 13, 2017
@medokin
Copy link
Contributor Author

medokin commented Mar 14, 2017

Perfect, thanks. It works fine now. Would be easier to contribute if #47 was finished.

@jaredcnance
Copy link
Contributor

#51 is open to resolve #47. However, it looks like AppVeyor has yet to upgrade their version of the SDK. Once that is fixed, I'll merge into master. Until then, if you'd like to contribute, you can work off the develop branch

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

Successfully merging this pull request may close these issues.

2 participants