feat(marketing): add hint text below Go page form labels - #48824
Merged
Conversation
Add a `hint` field to the Go page form schema, rendered as small italic text directly beneath the label and above the input. Use it on the Partner Day RSVP's "attending" field to move the "your Partner Day invite covers it" note out of the question itself.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📝 WalkthroughWalkthroughThe shared form schema supports optional hint text. The marketing form renders hints below non-checkbox labels. The Partner Day RSVP field separates its attendance label from the invite coverage details. ChangesForm Hint Support
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Fold in the wording tweak from #48821 ("Would you like to attend" instead of "Are you attending") now that this branch owns the attending field's label/hint split.
ana1337x
approved these changes
Aug 6, 2026
shaziyabandukia
enabled auto-merge (squash)
August 6, 2026 22:24
Contributor
Braintrust eval report
|
hunleyd
added a commit
that referenced
this pull request
Aug 8, 2026
…for-pitr-archiving-stale * origin/master: (342 commits) feat(studio): role-aware access feedback in scoped token creation (#48858) Initialize notebook editor page (#48842) test(docs): scan changed pages for WCAG 2.1 A/AA in warn mode (#48727) docs(auth): clarify audit logs storage options and configuration (#48852) feat(studio): warn that scoped tokens don't support the MCP server (#48849) feat(studio): lifecycle and role-aware scoped token view sheet (#48848) feat(www): add Open Authorization Integration Addendum (#48804) feat(studio): add legacy token mode to scoped pat creation flow (#48844) Add blog post: Supabase is now a connector on Perplexity Computer (#48776) feat(studio): enforce expiry scoped pat (#48811) fix(studio): model scoped pat permissions as OR-of-AND alternatives - smaller version (#48809) fix(ui): opaque default button hover fills (#48837) fix(ui): restore normal alert text wrapping (#48840) feat: notebook content schema (#48813) fix(ui): remove extra spacing before custom reports section (#48796) feat(marketing): add hint text below Go page form labels (#48824) Initialize notebooks store (#48801) Use white wordmark for QA.tech primary logo (#48827) fix titleless Admonition alignment (#48784) fix inconsistent product menu dividers (#48787) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Small feature addition to
packages/marketing(Go page form schema/renderer), plus a copy/layout change on/go/select-2026/partner-day. Supersedes #48821 (closed), which is folded in here.What is the current behavior?
Go page form fields only support a
descriptionstring rendered below the input. There's no way to put a short note directly under a field's label, above the input — so the Partner Day RSVP's "attending" question crammed "(your Partner Day invite covers it)" into the question text itself.What is the new behavior?
hintstring to the Go page form field schema (packages/marketing/src/go/schemas.ts), rendered as small italic text directly beneath the label, above the input (packages/marketing/src/forms/MarketingForm.tsx).hint, so this is backward compatible — verifiedvip-experience's identical select field (nohintset) renders unchanged.Additional context
_gopages with form fields are unaffected.prettier --checkandtsc --noEmitboth pass on the changed files.Summary by CodeRabbit