RFC Proposal: Only ASCII-word-characters and dash are allowed in anchor names #64
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
…are allowed in anchor names"
perlpunk
approved these changes
Jul 23, 2020
ingydotnet
approved these changes
Jul 23, 2020
perlpunk
approved these changes
Jul 30, 2020
pantoniou
approved these changes
Jul 30, 2020
|
Merged as RFC-0003 |
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.
At the moment, an anchor name can consist of almost any printable character, with the following specific exceptions:
Some implementations support a stricter subset of characters.
LibYAML, for instance, only supports:
This freedom in anchor names is useless to the user, while making parsing more difficult.