You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: