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

Improve validation reporting #33

Open
mikir opened this issue Nov 14, 2024 · 0 comments
Open

Improve validation reporting #33

mikir opened this issue Nov 14, 2024 · 0 comments
Milestone

Comments

@mikir
Copy link
Collaborator

mikir commented Nov 14, 2024

Currently, the validation throws exceptions with message which does not identify uniquely the wrong field. This is because validation is called recursively and there is no way how to get the current "field path".

This can be improved by the implementation of the some path stack or similar which will be passed to each validation method. Or, probably even better, we can invent something like validation report which will be returned instead of the exception. Such approach can be used for reporting several issues in one validation call.

@mikir mikir added this to the Backlog milestone Nov 14, 2024
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