react-component / react-component/tabs
tabs are very tightly integrated with tabcontent
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 572
- Forks
- 241
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 4
Description
How can we separate TabContent as our tab content is very expensive to rerender every time? It might be the value of a prop that changes in the TabContent which doesn't need the component to destroyed and recreated instead of just update the value.
In fact, if we have one shared TabContent there would be a lot of performance that can be improved.
const TabContent = ({value) =>
<ExpansiveDiv>{value}<ExpansiveDiv>
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
Start by tracing how TabContent and ExpansiveDiv are rendered and how tab changes recreate the content. Define the performance behavior to preserve, then measure whether separating the shared TabContent avoids unnecessary destruction and recreation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100