You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2020. It is now read-only.
Along with the other purposed changes to make the client less cumbersome to use, authorization should be spooled internally.
currently, new Mixer.ChatService(client).join(channelId) retrieves the auth information translating to the client already having all necessary data to authorize, so why is it up to the project to queue authorization?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Along with the other purposed changes to make the client less cumbersome to use, authorization should be spooled internally.
currently,
new Mixer.ChatService(client).join(channelId)
retrieves the auth information translating to the client already having all necessary data to authorize, so why is it up to the project to queue authorization?The text was updated successfully, but these errors were encountered: