preactjs / preactjs/preact-devtools
Track which hook rerendered
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 345
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Love the rerender reasons feature! One additional feature that would be useful is to identify in the UX which hook rerender. Since hooks don't have names, providing the number would suffice. Making it clickable to focus on the component and right hook in the elements panel would be amazing!
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 with the existing rerender reasons feature and the developer-tools UX for the elements panel. Define how the UI should identify the hook number that caused a rerender and what clicking it should focus; done means the hook number is shown and the relevant component and hook can be focused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100