Avoid unnecessary rerenders with canAccess hooks when there is no authProvider #10200
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.
Problem
As we use react-query for the canAccess hooks, users may see at least one rerender because it run asynchronously.
Solution
Detect there is no support for canAccess and return a fake react-query result if needed.
How To Test
The
useCanAccess
anduseCanAccessResources
have stories with and without an AuthProvider that shows the behavior.Additional Checks
master
for a bugfix, ornext
for a feature