Ensure consistent string case for channel name checks #169
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.
We have
alveussanctuary
in the default set of channel names, so when the extension is active in this channel it should not be watching the extra channel names includingalveusgg
. However, as seen in recent collaborations, commands run inalveusgg
where controlling the extension inalveussanctuary
.After some investigation, the issue stems from the
broadcaster_name
foralveussanctuary
actually beingAlveusSanctuary
. I've solved this in a few different places for some redundancy -- switching tobroadcaster_login
gives us backalveussanctuary
instead, and then I've ensured we're normalizing all the values used for these name checks to always be lowercase.