Update open-close design doc to accept the hash & slash alternative #535
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
eemeli
added
design
mihnita
reviewed
Nov 27, 2023
eemeli
commented
Nov 28, 2023
Co-authored-by: Eemeli Aro <[email protected]>
|
During the teleconference on Monday I supported merging this PR as proposed. However, I had forgotten about this part:
I think we should phrase this differently. Right now, the doc recognizes that standalone elements are still an open question, but the documented proposal goes one step further: it suggests to use the registry to encode the standalone aspect. I filed #542 with my suggestion for how to improve the doc. |
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 reflects the consensus reached during the 2023-11-20 call, to accept
{#foo}...{/foo}as the open-close syntax.The previously proposed
{#foo/}syntax for standalone elements did not reach consensus, and so is left out here.Examples are updated to use the new syntax, and the
{+foo}...{-foo}alternative is documented as such.