We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
current behaviour when there is a validation error is that it returns a 502
the enhancement i propose is that the returned payload contains a structured error containning this list of failures , as well as the payload
this allow to have an off line diagnotics without the usuage of the (nice) UI
context of usage beeing newman + wiretap in CICD
given the fact that in case of error newman log the payload, it allows to understand that there was an error, and then to diagnose
it may requires a dedicated flag
The text was updated successfully, but these errors were encountered:
No branches or pull requests
current behaviour when there is a validation error is that it returns a 502
the enhancement i propose is that the returned payload contains
a structured error containning this list of failures , as well as the payload
this allow to have an off line diagnotics without the usuage of the (nice) UI
context of usage beeing newman + wiretap in CICD
given the fact that in case of error newman log the payload, it allows to understand that there was an error, and then to diagnose
it may requires a dedicated flag
The text was updated successfully, but these errors were encountered: