-
Notifications
You must be signed in to change notification settings - Fork 393
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
Improve input validation error messages #3752
Comments
tchiotludo
added a commit
that referenced
this issue
May 24, 2024
tchiotludo
added a commit
that referenced
this issue
May 24, 2024
tchiotludo
added a commit
that referenced
this issue
May 24, 2024
tchiotludo
added a commit
that referenced
this issue
May 24, 2024
tchiotludo
added a commit
that referenced
this issue
May 24, 2024
tchiotludo
added a commit
that referenced
this issue
May 24, 2024
tchiotludo
added a commit
that referenced
this issue
May 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, invalid inputs generate either blank error messages like this one (just 500 response without any details):
or not specific enough as here where input "nr" should be integer but got a string:
Expected outcome
The error message should clarify:
A friendlier error message schema:
Invalid input for '<input_id>': expected <expected_type> but received "<received value>"
The text was updated successfully, but these errors were encountered: