buck2_validation: tweak and slightly improve error message #769
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
facebook-github-bot
added
the
CLA Signed
thoughtpolice
force-pushed
the
aseipp/push-uxtzlovqlops
branch
4 times, most recently
from
b7f8aaf
to
d93ae63
Compare
Previously, when using `ValidationInfo()` with a failure, it ends up turning out
an awkward message that turns
{ "status": "failure", "message": "you failed the test!" }
into
"you failed the test!".
After this patch, it comes out as:
you failed the test!
Which seems much more reasonable and easy to parse. It also gives the validation
message more control over the punctuation.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
thoughtpolice
force-pushed
the
aseipp/push-uxtzlovqlops
branch
from
d93ae63
to
24e0bcf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, when using
ValidationInfo()with a failure, it ends up turning out an awkward message that turnsinto
After this patch, it comes out as:
Which seems much more reasonable and easy to parse. It also gives the validation message more control over the punctuation.