-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert renaming of useEntityId hook #39683
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Riad makes good point here - #39681 (comment), so reverting the change makes sense to me. |
Size Change: -3 B (0%) Total Size: 1.21 MB
ℹ️ View Unchanged
|
7a538ac
to
87dfc42
Compare
I've rebased this in the hope that it will get the RN tests to run. @draganescu please feel free to merge when it's green. |
Looks to be failing due to #39689. Will need to merge that one and rebase this one to get the e2e tests to pass. |
What?
Alternative to #39681.
This PR reverts the renaming of
useEntityId
back to the original.Why?
This hook is part of the public API of
@wordpress/core-data
but it has been removed in favour ofuseEntityProviderId
without the formal deprecation process.This was caught as part of a fix to the Navigation block which broke when the hook was removed.
It has been suggested that renaming to include the "provider" term exposes implementation details to the consumer.
As the folks who worked on the original PR aren't available right now, it was deemed the simplest option simply to revert the rename of this one hook for now. @adamziel can always resubmit a PR to rename again later.
How?
This PR takes the approach suggested by @youknowriad in #39681 (comment) which is simply to rename the hook back to the original.
Testing Instructions
Start empty
Advanced
panel of block's Inspector controlstrunk
it crashes)Screenshots or screencast