improve error reporting JSON vs YAML about yaml HOT 6 CLOSED

/kind cleanup
/priority important-longterm

from yaml.

It would be great if we could fix this, the error messages are very very confusing to end-users.

from yaml.

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
/kind design
/remove-priority important-longterm
/priority backlog

from yaml.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from yaml.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from yaml.

as explained here this is far from ideal:
#9 (comment)

if someone wishes to help please open tickets for yaml v2/v3 and json-iter.

from yaml.