@zen-agentchecks…zen/dashboard-field-regex-validation-myd3ns → main5 files · +44 −1updated 2mo agoAdd inline client-side validation for connection field values (subdomains, API keys, etc.) on both the link auth page and developer dashboard forms. When a toolkit field has regex and expected_format metadata from the API, the form now:
This is the frontend companion to ComposioHQ/hermes#9115 which added server-side regex validation.
Files changed:
link-screen.tsx / types.ts — Added regex and expected_format to field type definitionsform-content.tsx — Added validate function to register() with regex check, and shows expected_format hintschema.ts — Added .refine() with regex validation to buildFieldValuesSchemacredential-field.tsx — Shows expected_format hint below field descriptionpnpm lint — no errors on changed files (pre-existing errors only)pnpm typecheck — no errors on changed files (pre-existing errors only)^[a-zA-Z0-9][a-zA-Z0-9-]*$):
https://my-company.freshdesk.com) → red error "Just the subdomain (e.g. 'mycompany'), not the full URL", form blockedmy-company) → error clears, hint shows in neutral grayexpected_format hint displays in gray when no error, replaced by red error text on validation failureexpected_format stringsAddressed Bugbot's review comment about empty expected_format strings:
form-content.tsx: Changed ?? to || so empty string falls back to "Invalid format for ..."schema.ts: Added && field.expected_format truthy check to the existing guardFixed in 96b94cc0.
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard |  Error | Apr 8, 2026 0:27am |