require test point ID or hyphen-minus when description exists #46
Conversation
This file contains hidden or 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
This avoids parsing ambiguity:
1..1
ok 1 is less than 2
Is "1" part of the description, or is it the test point ID? This
change makes it clear that the "1" is the test point ID, and the
description is "is less than 2". To force the "1" to be part of the
description, that line should read:
ok - 1 is less than 2
or:
ok 1 1 is less than 2
or (preferred):
ok 1 - 1 is less than 2
|
Yeah, it makes sense for future versions of TAP to require this. |
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.
This avoids parsing ambiguity:
Is "1" part of the description, or is it the test point ID? This change makes it clear that the "1" is the test point ID, and the description is "is less than 2". To force the "1" to be part of the description, that line should read:
or:
or (preferred):