[material-ui][Tabs] Ensure consistent TypeScript type for the `value` prop across all tab-related components
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Current behavior
The value type varies inconsistently across tab-related components.
Expected behavior
For consistency, the value type should universally be string | number for all tab-related components. However, for the Tabs component specifically, it should accept string | number | null.
Context
Refer to this comment in issue #40630.
Search keywords: tab, value prop
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 referenced comment in issue #40630, then search the material-ui repository for value prop type declarations across the tab-related components. Confirm the current differences and update the declarations so related components use string | number, while Tabs also accepts null; done means the public TypeScript types are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100