Open danielhelfand opened 3 years ago
cc @jorgemoralespou
Related #311?
Noting for this issue that we may want to consider investigating other ytt errors as well.
cc @pivotaljohn
I guess it depends on how those error messages are viewed. If kctrl
prints such error messages, interpreting escape characters (like \n
), might be just great.
Bigger picture, folks in ytt have talked about providing a structured output for error messages as well, separating the content of the messages from their format. But we've had our hands full enough that it hasn't made sense to (yet) invest further into the needs, there.
One question that came up in the Carvel community meeting is what ytt schema errors look like when seen via a PackageInstall/App status. We do not currently have any testing in place for ytt schemas with kapp-controller so it might be worthwhile to add error case tests to assess if the UX is consumable for users. It would also be helpful to manually view statuses to assess if the information is easy to follow when errors happen.
More on schemas in docs here: https://carvel.dev/ytt/docs/latest/how-to-write-schema/#docs
One particular issue I was wondering about is what if there are many schema validation errors? Would all of that information be overwhelming to users?
Acceptance Criteria