Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support “named hooks” in DevTools extension #38

Open
mkcode opened this issue Sep 29, 2020 · 0 comments
Open

Support “named hooks” in DevTools extension #38

mkcode opened this issue Sep 29, 2020 · 0 comments

Comments

@mkcode
Copy link
Collaborator

mkcode commented Sep 29, 2020

Summary:

Showing hook “names” in the DevTools component inspector and Profiler is an often requested feature, but has been blocked on the creation of a parser that’s capable of inferring the names of hooks based on the variable names their values get assigned to. This project would be to implement the parser in DevTools (16474) and optionally, if there was enough remaining time, show the new name metadata in the Profiler (16477) (Note that this project is largely a research project. It’s also intended to be an alternative choice to the Profiler task above, not an additional one. I only have the bandwidth to support one project.)

Level of complexity: High

Experience

With the following would be a big plus:

Developing/debugging Chrome web extensions
Working with ASTs

Deliverables

DevTools code to load source code (with source maps), parse it, and infer names of hooks.
Changes in DevTools UI (Components tree) to show parsed names in the component inspector.
Optional Profiler updates as well to show the names of hooks that changed in a commit (similar to how we show props and class-state names).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant