useEntityRecord: Fix destructure error when enabled option is false
#51534
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.
Fixes: #51466
Related to #39288
What?
This PR fixes an error that occurs when
{ enabled: false }is specified in the fourth argument ofuseEntityRecord.For example, when you write code like this:
The following error is logged in the browser console:
Why?
This is because if
enabedisfalse, the internaluseQuerySelectreturnsnulland thedataproperty cannot be destructured.How?
I referred to getEntityRecords implementation, but I think it should be the value of the
dataproperty that is null, not the entire object.Testing Instructions
Confirm that the following code does not cause an error.
The
recordvariable should be the post object if the post exists, orundefinedif it does not:The
recordvariable should always benull: