Skip to content
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

Potentially add actual type in MultipeInvalid exception #394

Open
rawrgulmuffins opened this issue Apr 10, 2019 · 1 comment
Open

Potentially add actual type in MultipeInvalid exception #394

rawrgulmuffins opened this issue Apr 10, 2019 · 1 comment

Comments

@rawrgulmuffins
Copy link

Given the following error message

voluptuous.error.MultipleInvalid: expected str for dictionary value @ data['timeRange']

It would be useful to modify the message to say

voluptuous.error.MultipleInvalid: expected str for dictionary value @ data['timeRange'] but found int instead
@rawrgulmuffins
Copy link
Author

Related, consider adding actual values for not valid value for dictionary value.

Current Error

voluptuous.error.MultipleInvalid: not a valid value for dictionary value @ data['httpReceiptTime']

Proposed Modification

voluptuous.error.MultipleInvalid: not a valid value (`None`) for dictionary value @ data['httpReceiptTime']

OR

voluptuous.error.MultipleInvalid: not a valid value for dictionary value @ data['httpReceiptTime']. Found `None`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant