Show useSelector result in React DevTools #1530
Merged
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.
Resolves #1525
I've checked the performance impact by calling
useSelector
10000 times while rendering 1 component. Durations during mounts and updates:The times vary a lot on each run so I've concluded that there is no noticeable performance difference and left the
useDebugValue
to be called regardless.The benchmark code
Please consider that
useDebugValue
gives no effect with a React production bundle.I haven't found a way to test a
useDebugValue
call therefore I haven't added a test. I will add if I know how.