Take advantage of useDebugValue to display data in devtools #193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're taking advantage of React's useDebugValue hook here in order to display contextual tracking data when a user inspects the hook in React devtools. 2 open questions:
Is it necessary for us to call this twice? I like having it in the higher-levelDecided to remove from theuseTrackinghook because it makes it more discoverable. Otherwise, devs would need to inspect the nesteduseTrackingImplhook in order to discover it. I added it also touseTrackingImplbecause that makes it visible for components that are using the HoC rather than the hook, since that hook is shared between both. It's redundant, but covers both use cases. Def open to thoughts on this.useTrackingImplhook—I don't think devs would expect to see it there for a component using the decorator so it probably wouldn't get much use.Screenshot