feat(irc framework): support (client) tags #4774
Open
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
RaitoBezarius
force-pushed
the
client-tags
branch
4 times, most recently
from
da7e41e
to
ac5eb00
Compare
|
I have kiwiirc/irc-framework#366 and some code for this PR to support client tag denies more properly, but I think it's better to do it in another PR. |
brunnre8
requested changes
Aug 12, 2023
It is now possible to receive, send and process client tags in general using the IRC framework. This is useful for many client-oriented IRCv3 features: typing, reacts, replies, channel contexts, etc.
RaitoBezarius
force-pushed
the
client-tags
branch
from
ac5eb00
to
ab678f1
Compare
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.
It is now possible to receive, send and process client tags in general using the IRC framework, adds also TAGMSG.
This is useful for many client-oriented IRCv3 features: typing, reacts, replies, channel contexts, etc.
This is step 1 for #2419 which I will slowly but surely finish.