-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Restream Support #104
Add Restream Support #104
Conversation
You can remove the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the testing and CI fix, you could update JWTKit to v5, although it may bring breaking changes.
…function Co-authored-by: Francesco Paolo Severino <96546612+fpseverino@users.noreply.github.com>
@fpseverino, Thanks for the feedback. Given that the current PR focuses on adding a new auth provider, it might be better to handle JWT updates in a separate PR. This will keep our changes focused and easier to review. I'll create a new PR for updating JWTKit to v5 and address any potential breaking changes. |
Co-authored-by: Francesco Paolo Severino <96546612+fpseverino@users.noreply.github.com>
Just an FYI I'm going to be doing an Imperial code sprint next week to go through all the issues and PRs |
This PR adds support for Restream OAuth integration to the Imperial package.
Depends on