-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
useInnerBlocksProps: stabilise dropZoneElement prop #56313
Conversation
Size Change: -5 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
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.
Given #56312 and the explanation in these comments this looks like the best solution 👍
Side note: I wonder if we should go through these other unstable props and stabilise or remove them as the case may be (we'll probably have to stabilise as they are in practice public APIs and have been for a while)
Wonderful, thanks for the quick review @tellthemachines! 🙇
I'm leaning that way, too. Let's see if we get any further comments overnight, and if not, I'll plan to merge this PR in tomorrow.
Good question: I think the |
What?
Alternative to #56308, which sought to make
dropZoneElement
private, this PR proposes stabilising the prop instead.Happy for any feedback, ideas, or opinions on whether it's better to go private for now, or to stabilise the prop!
Why?
Based on discussion in #56070 (comment) there's a good case to be made that we will need
dropZoneElement
as a stable prop inuseInnerBlocksProps
. See the prototype in #56312 for an example use case, which would be part of resolving #26049.How?
__unstableDropZoneElement
todropZoneElement
Testing Instructions
Same testing steps as #56070: