[Tabs] Evaluate use cases and options for declarative-show-hide functionality
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Based on the needs from the tabs research, we believe that there is a common show-hide functionality which enables many tab components to be built. We have compiled a list of ways in which that content could be build from using existing primitives to inventing new ones at https://github.com/flackr/declarative-show-hide .
We would like to evaluate the options, whether we have missed any requirements or if any of the existing requirements are unnecessary and identify our best options moving forward for implementing tab components.
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
Start with the declarative-show-hide proposal linked in the issue and compare its listed approaches against tab use cases and requirements. Document any missing or unnecessary requirements and recommend the best option for implementing tab components.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100