Skip to content

@hanzo/ui 8.32.1: SignInPanel takes the site's own IAM client - #314

Merged
Darkhorse7stars merged 1 commit into
mainfrom
signin-panel-request
Nov 11, 2026
Merged

Darkhorse7stars merged 1 commit into
mainfrom
signin-panel-request

Conversation

@Darkhorse7stars

Copy link
Copy Markdown
Member

Why

8.32.0's SignInPanel (#313) reads its client from useIam(), which throws outside an <IamProvider>. hanzo.team (Vite) holds its own IAM client and mounts no provider, so it cannot draw the panel.

What

  • New optional prop request: the function that mints the site's own authorize request (its client's getSigninUrl; PKCE verifier and state stay on the site).
  • With no request, under a provider, the provider's client mints it as before (hanzo-inc/app unchanged).
  • 8.32.0 → 8.32.1.

Testing

vitest run src/auth/signin-panel.test.tsx: 7 passed, including a new case where the site passes its own client and an email leaves for hanzo.ai/login with login_hint. tsc: no errors in the panel files.

8.32.0's panel read its client from useIam(), which throws outside an
<IamProvider>. hanzo.team holds its own IAM client and mounts no provider, so it
could not draw the panel. A `request` prop now takes the function that mints the
site's own authorize request (its client's getSigninUrl, which keeps the PKCE
verifier and state on the site); under a provider, with no `request`, the
provider's client mints it as before.
@Darkhorse7stars
Darkhorse7stars merged commit 6d8113f into main Nov 11, 2026
5 checks passed
@Darkhorse7stars
Darkhorse7stars deleted the signin-panel-request branch November 11, 2026 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant