-
Notifications
You must be signed in to change notification settings - Fork 3.6k
fix: added 'enable_granular_consent' parameter #2582
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
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!
-- conventional-commit-lint bot
https://conventionalcommits.org/
* origin/main: Added 'enable_granular_consent' parameter
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 seems good but, I can't find any documentation on the Google auth side regarding the enable_granular_consent parameter. Can you show me where you see this documented, so I can be sure it's correct?
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 changelog gets updated automatically through our release-please bot. We can revert this change.
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.
Tuanis
commented
May 2, 2024
Here's one link to documentation regarding the enable_granular_consent parameter
I have found that in SDK missed parameter
enable_granular_consent. I've added this parameters to Client's configuration. Please review.