oxidecomputer / oxidecomputer/console
Input component consistency
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
Each of our inputs is structured slightly different – the TextField for example has the FieldLabel in the field component but the combobox has it on the base Combobox component.
Would be helpful to formalise the relationship between these and also be a bit more consistent with which props are optional.
Contributor guide
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
Compare the structures of the TextField, FieldLabel, and Combobox components, including where FieldLabel is attached and which props are optional. Done means the relationship between these components is formalized and input components follow a consistent optional-prop approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100