Skip to content

fix(react): run registry actions without a state setter - #358

Open
Yi-111-a wants to merge 1 commit into
vercel-labs:mainfrom
Yi-111-a:fix/define-registry-no-state-setter
Open

Yi-111-a wants to merge 1 commit into
vercel-labs:mainfrom
Yi-111-a:fix/define-registry-no-state-setter

Conversation

@Yi-111-a

@Yi-111-a Yi-111-a commented Sep 24, 2026 •

Copy link
Copy Markdown

Fixes #354

Summary

  • execute catalog actions even when getSetState() returns undefined
  • pass a no-op state setter so actions that update state remain safe
  • add regression coverage for the stateless handler path

Verification

  • focused React renderer tests: 9 passed
  • source-only TypeScript check: passed
  • Prettier check: passed
  • full pnpm lint and pnpm type-check could not run in this VM because the repository requires Node 24+ and the full dependency install exhausted the available disk

AI disclosure: I used OpenCode (opencode/space-bunny-free) to inspect, implement, and verify this change.

@vercel

vercel Bot commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

@Yi-111-a is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

This branch has not been deployed

No deployments
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.

handlers() silently drops actions when getSetState() returns undefined

1 participant