Describe the feature
I have been building react now for two years. For much of this time, I figured I could have one hook per module that serves all the components, putting ALL of the api's / helper methods / state variables , etc related to the module within the same hook.
I now know that is NOT how it should be done, after doing a bit of research, and that hooks should generally be granular.
I could probably communicate this better if more information is requested, but I was wondering if these hook/component instances could be tracked and portrayed somehow on the Million dashboard to give developers an understanding of how much memory is being allocated to these layers of the React tree.
If this is unrelated to this project, please help me understand where this could fit into the react dev tools that exist today.
Thanks!
Additional information
Describe the feature
I have been building react now for two years. For much of this time, I figured I could have one hook per module that serves all the components, putting ALL of the api's / helper methods / state variables , etc related to the module within the same hook.
I now know that is NOT how it should be done, after doing a bit of research, and that hooks should generally be granular.
I could probably communicate this better if more information is requested, but I was wondering if these hook/component instances could be tracked and portrayed somehow on the Million dashboard to give developers an understanding of how much memory is being allocated to these layers of the React tree.
If this is unrelated to this project, please help me understand where this could fit into the react dev tools that exist today.
Thanks!
Additional information