Provide full integration for Chakra UI and RedwoodJS' form components
Open
Nobody has claimed this yet.
front-end
good first issue
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
In other words, integrate Chakra UI's form components with
react-hook-form.
- - Ensure all components favor the name prop when provided, not the
useFieldNamehook's value. - - Once complete, extract-out components into a library.
- - Ensure all components integrate with Chakra UI's
isInvalid,isRequired, ... props. - - Integrate the following components:
- - Button (Submit)
- - Checkbox
- - Editable
- - Form Control
- - Input
- - Number Input
- - Pin Input
- - Radio
- - Range Slider
- - Select
- - Slider
- - Switch
- - Textarea
Optional Components (provided as Recipes)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by reviewing the existing Button, Form Control, Input, and Select integrations alongside the linked RedwoodJS, Chakra UI, and react-hook-form documentation. Done means the remaining listed form components support the required naming and Chakra props, and the integrations are extracted into a library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100