feat: Send messages using Helix API #5200
Merged
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
Wissididom
reviewed
Feb 25, 2024
pajlada
reviewed
Feb 25, 2024
pajlada
reviewed
Feb 25, 2024
pajlada
reviewed
Feb 25, 2024
pajlada
approved these changes
Feb 25, 2024
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 changes the default way messages are sent to use the Helix API instead of IRC. There's still an option to use IRC.
I decided to use a struct as the parameters to the Helix call to make help callers get the order right (using
{.property = value}), since it would be fourQStringvalues in a row.This augments #4962.
Fixes #5127.