-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[google_sign_in_web] Add plugin_name to init call.
#5242
Conversation
|
How does this work? Is this a special value that's whitelisted on the server side? |
@stuartmorgan The presence of the key with any (unique-ish) value is an escape hatch to let the backend know that we need more time to do the actual migration to the new API. If not present, new ((Apologies for the internal link, but) please do check cl/439406676 for the documentation CL, it'll be published soon) |
stuartmorgan-g
left a comment
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.
LGTM with nits.
(Is it normal for us to be editing files in src/generated, or is this a special case?)
@stuartmorgan Fair question. These files used to be generated when the plugin got started, but the generator hasn't kept up with the changes we needed to do. They probably should be moved out of Created this issue to track cleanup: flutter/flutter#101855 |
This change ensures that a
plugin_nameattribute with a known value is passed to theinitcall of the current Web implementation of Google Sign In JS SDK.This allows "new applications to continue using the plugin after April 30th, 2022".
Mitigates: flutter/flutter#88084
See also: flutter/flutter#101004
//FYI @brdaugherty @kevmoo
Pre-launch Checklist
dart format.)[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style.///).If you need help, consider asking for advice on the #hackers-new channel on Discord.