We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
API Platform version(s) affected: 3.2.18
Description If you have seld/jsonlint installed, since https://symfony.com/blog/new-in-symfony-6-4-serializer-improvements#detailed-json-decoding-errors in dev mode symfony serializer is supposed show something more useful than "Syntax error"
seld/jsonlint
This can also be enabled in production by using this config:
framework: serializer: default_context: php/const Symfony\Component\Serializer\Encoder\JsonDecode::DETAILED_ERROR_MESSAGES: true
Neither works with APIP, however.
How to reproduce Install seld/jsonlint and send payload to APIP endpoint that's not a valid JSON
The text was updated successfully, but these errors were encountered:
Whoops, this was a typo on our side should be !php/const instead of php/const
!php/const
php/const
Sorry, something went wrong.
No branches or pull requests
API Platform version(s) affected: 3.2.18
Description
If you have
seld/jsonlint
installed, since https://symfony.com/blog/new-in-symfony-6-4-serializer-improvements#detailed-json-decoding-errors in dev mode symfony serializer is supposed show something more useful than "Syntax error"This can also be enabled in production by using this config:
Neither works with APIP, however.
How to reproduce
Install seld/jsonlint and send payload to APIP endpoint that's not a valid JSON
The text was updated successfully, but these errors were encountered: