Genericize cap parsing and negotiation #79
Draft
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
Expand cap parsing to allow for caps with a value, and add an option to specify more capabilities to negotiate with the server.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Expand cap parsing to allow for caps with a value, and add an option to specify
more capabilities to negotiate with the server.
Fixes #78
I'm making this a WIP for now for a couple reasons:
Client.opt.saslentirely to force things to adopt the new way of passing aSetof caps toClient. I could do a deprecation thing where the constructor adds opt.sasl to opt.capabilities, but since the only thing using this is matrix-appservice-irc I don't think there's a need to postpone the removal. However if that's something you want, I can add it in.