Improved error message when a mandatory flag is missing #1429
Assignees
Comments
harshadixit12
added a commit
that referenced
this issue
Jan 9, 2025
…onvert (#1429) When mandatory flags for file convert are missing, the error message is not helpful. In this commit, we have added additional validation to communicate more details in the message.
5 tasks
harshadixit12
added a commit
that referenced
this issue
Jan 10, 2025
…onvert (#1429) When mandatory flags for file convert are missing, the error message is not helpful. In this commit, we have added additional validation to communicate more details in the message.
harshadixit12
added a commit
that referenced
this issue
Jan 10, 2025
…onvert (#1429) When mandatory flags for file convert are missing, the error message is not helpful. In this commit, we have added additional validation to communicate more details in the message.
harshadixit12
added a commit
that referenced
this issue
Jan 15, 2025
…onvert (#1429) (#1487) * fix: improve error messaging when mandatory flag is missing in file convert (#1429) When mandatory flags for file convert are missing, the error message is not helpful. In this commit, we have added additional validation to communicate more details in the message. * add a reusable validation function for strings * assert converted file contents and address review feedback * limit file convert tests to yaml format for now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a mandatory CLI flag is missing, the error message is not helpful:
It would help to add the name of the field, e.g.
The text was updated successfully, but these errors were encountered: