Fix registry.dtd to not use alternatives in function, formatSignature, matchSignature #434
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.
A spin-off from #420, in which @mihnita noticed that
registry.dtd
uses alternatives in a wrong way. For example,<!ELEMENT formatSignature (input?|option*)>
means thatformatSignature
is allowed to have as children either: at most oneinput
OR any number ofoptions
, but not both.Instead, @mihnita suggested using sequences:
<!ELEMENT formatSignature (input?,option*)>
, which this PR does. Note that sequences require the children to appear in a specific order, which isn't something that's useful to us. However, I'm not aware of any way of lifting this requirement that also allows to enforce at most oninput
or exactly onedescription
.