api: set rfc_7807_compliant_errors to true #7084
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It was a little tricky, but finally i figured out how to do it: https://api-platform.com/docs/core/errors/ The big impact is, that the serialization of the errors is now done with the same infrastructure as serializing entities. That makes it less format dependent. It seems a little weird that we use a provider to "replace" the exception path of the response by extracting the exception to the context, and then continuing like when we would serialize a response. But i can also see the benefits. See api-platform/core#5974 Issue: ecamp#6618
⛔ Feature branch deployment currently inactive.If the PR is still open, you can add the |
BacLuc
force-pushed
the
migrate-rfc-compliant-errors
branch
from
8c234a9 to
b1de32a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was a little tricky, but finally i figured out how to do it: https://api-platform.com/docs/core/errors/
The big impact is, that the serialization of the errors is now done with the same infrastructure as serializing entities. That makes it less format dependent.
It seems a little weird that we use a provider to "replace" the exception path of the response by extracting the exception of the context, and then continuing like when we would serialize a response. But i can also see the benefits.
See api-platform/core#5974
Issue: #6618