Ratify the reply client tag specification. #535
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
|
The only concern I have is do we want to prohibit multi level replies. I would favour doing so, but if not then we might need another tag to indicate the top level of a reply chain. If we do prohibit them, then react would have to override that rule. |
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.
I don't think there are any objections relating to this and we have enough implementations so lets ratify and ship it!
Known implementations
Unchecked means incomplete or an intent to implement has been expressed. The numbers indicate minimum requirements. Any others?
Client (3/1)
Server (3/2)
This one is a client-only tag so server implementations are generally less important imo.
Bots