-
Notifications
You must be signed in to change notification settings - Fork 947
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: adds react hook form to product general settings #2677
Conversation
The latest updates on your projects. Learn more about Vercel for Git 鈫楋笌 2 Ignored Deployments
|
Thank you for following the naming conventions for pull request titles! 馃檹 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pandeymangg Nice, it's coming together 馃殌 A quick review and question :-) I also need to dig a little deeper into the react hook form to see how we can tweak it.
I think since this is kind of a reference design for how we do forms in Formbricks, it should be as good and well thought out as possible 馃槉
isProductNameEditDisabled: boolean; | ||
}; | ||
|
||
const editProductNameSchema = ZProduct.pick({ name: true }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be more consistent if we name this e.g. ZProductNameInput
or similar that we know that this is a zod type.
...eb/app/(app)/environments/[environmentId]/product/general/components/EditProductNameForm.tsx
Outdated
Show resolved
Hide resolved
(cherry picked from commit 6d6a47a)
What does this PR do?
Adds react hook form support for the product look and feel setting's placement form, and refactors the product general settings to use the zod resolver with react hook form
How should this be tested?
Checklist
Required
pnpm build
console.logs
git pull origin main
Appreciated