Implication of new Google In API?

[louis030195]

trafficstars

Hi! Thanks for the great lib. I was wondering what does it imply for it regarding the incoming migration from Google Identity?

The goal

Clarifications, will this lib break, or need some changes, or just optional changes.

[ph-fritsche]

This library will need changes prior to 2023-03-31. The gapi.load and gapi.client will continue to work, but references to gapi.auth2 need to be replaced. There is a migration guide.

This will be a breaking change, but I'd like to keep the pattern "Give me the gapi module when it's ready with the scopes and client modules I require". The new hook should probably look like const { gapi, google } = useGoogleApi({/*...*/}) and accept the same options. Users could then access GIS per google.accounts. where they accessed gapi.auth2 before.

[socketopp]

This library will need changes prior to 2023-03-31. The gapi.load and gapi.client will continue to work, but references to gapi.auth2 need to be replaced. There is a migration guide.

This will be a breaking change, but I'd like to keep the pattern "Give me the gapi module when it's ready with the scopes and client modules I require". The new hook should probably look like const { gapi, google } = useGoogleApi({/*...*/}) and accept the same options. Users could then access GIS per google.accounts. where they accessed gapi.auth2 before.

Is that something that is going to be released soon to react-gapi?