-
Notifications
You must be signed in to change notification settings - Fork 75
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 error reporting JSON vs YAML #9
Comments
/kind cleanup |
It would be great if we could fix this, the error messages are very very confusing to end-users. |
problem here is that all the backends out there including encoding/json yaml.2/3, json-iter don't have good typed errors. this leaves us in a space where we need to parse strings, modify them and return proper errors. i'm -1 on that, so it's probably best to wait on the backends to fix them, or attempt to push patches upstream. /remove-kind cleanup |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
as explained here this is far from ideal: if someone wishes to help please open tickets for yaml v2/v3 and json-iter. |
the errors of this library need work.
with the strict JSON decoder unknown fields would result in errors such as:
this gives a hint that "z" is unknown.
but the user would first of all be confused why is the error throw to stdout about JSON, while their e.g. manifest is in YAML.
xref: #7
The text was updated successfully, but these errors were encountered: