-
Notifications
You must be signed in to change notification settings - Fork 25
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
Minor issues with error messages #121
Comments
Do you have examples? We have a bunch of test cases for these responses. Are we missing some? |
Some of them are there -
|
Opened a PR to the library that raises these errors... ota42y/openapi_parser#55 |
@bdunne Can this be closed now? |
Was reviewing some API things with @psav and we noticed a few minor oddities:
When you pass invalid fields (readonly for example) in a POST request, the error string that comes back has the values as symbols. However this is strange from non-Ruby clients where symbols aren't a thing (nor or they even a thing in JSON). These should be changed in the error message to just strings.
If a null value is passed to a non-nullable field the error message is strange. Something like
a, b, c: don't accept null
cc @bdunne
The text was updated successfully, but these errors were encountered: