-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support upstream League Oauth2 Clients. #3
Conversation
Ping for review @weierophinney |
Find any time to review this @weierophinney ? :) |
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.
This looks fantastic, @nynka! I've flagged a few documentation changes, but once those are ready, I'm ready to merge this and release a new major version.
- Remove implementation and test details in changelog - Fix typos "Client/client", "s/inherits/inherit/"
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.
The suggestions look good - get them pushed, and I can merge and release!
- Link to the relevant documentation (full URL) in changelog - Explanation of the "custom" provider
Consider it done. Thank you for great feedback! @weierophinney |
This patch updates the CHANGELOG entries for #3 to reference the pull request, so users can understand the source of the change. Additionally, it pushes the new version entry to the top of the file (CHANGELOG.md files list in reverse chronological order), sets the version to 2.0.0, and sets the release date.
This new feature adds the ability to use any League Oauth2 Client that inherits from League\OAuth2\Client\Provider\AbstractProvider by adding providers of their choice to their local configuration.
Are you fixing a bug?
master
branch, and submit against that branch.CHANGELOG.md
entry for the fix.Are you creating a new feature?
develop
branch, and submit against that branch.CHANGELOG.md
entry for the new feature.Is this related to quality assurance?
Is this related to documentation?