fix(GoogleLogin): guarantee credential presence onSuccess

[zetlen]

Add a type assertion to the signature of onSuccess of the GoogleLogin component to reflect that the credentialResponse.credential will always be present if the handler is called.

The callback handler in the GoogleLogin component checks that the credentialResponse.credential is truthy, so it can't be the empty string when passed to onSuccess:

    if (!credentialResponse?.credential) {
      return onErrorRef.current?.();
    }

    const { credential, select_by } = credentialResponse;
    onSuccessRef.current({
      credential,
      clientId: extractClientId(credentialResponse),
      select_by,
    });

Since the code guarantees this, the onSuccess handler shouldn't have to assert that the credential is present again. This PR adjusts the type of the parameter to onSuccess so that the credential property is always truthy.

[changeset-bot]

🦋 Changeset detected

Latest commit: f0cec05

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@react-oauth/google	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-oauth	❌ Failed (Inspect)			Mar 19, 2025 6:49pm

[zetlen]

Not sure why the deployment is failing, let me know what I can do!

[angelliambo]

sorry for not be helpfull to solve this problem, but I actually need this fix . mabe try to build a new pr :D

[vercel]

@zetlen-dandy is attempting to deploy a commit to the momensherif's projects Team on Vercel.

A member of the Team first needs to authorize it.