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
PUT on /resource/non-existing-id should work according to the HTTP spec #4344
Comments
Do you mean that the request must create if it does not exist ? If so, I am a bit worried:
thanks in advance for your answer |
Basically our current To prevent any BC break, we plan to introduce a new attribute in 2.7 (set to false by default, but triggering a deprecation warning is not set to true) to enable the standard behavior (if set to false, the current behavior will be preserved). In 3.0 we'll remove the non-standard behavior. |
Ok I see. I'll take a look at the PATCH method then. Thanks |
See https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.4
probably using
merge
in Doctrine.The text was updated successfully, but these errors were encountered: