Normalize on RFC <number>
#15
Merged
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.
Refs: nodejs/node#26695 (comment)
The first commit prohibits
rfc
andRfc
to enforce uppercaseRFC
.As of nodejs/node@3b6344c this gives:
The second commit enforces a space between
RFC
and the number. This is possibly an abuse of prohibited-strings, but it does catch the cases where the space is omitted (the user message isn't that clear, especially if you are unfamiliar with regular expressions). As of nodejs/node@3b6344c: