-
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
Blocks: Remove no longer used Block Content Context #41395
Conversation
Size Change: -149 B (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
84d6572
to
dfd2c75
Compare
@@ -902,12 +902,18 @@ _Returns_ | |||
|
|||
### withBlockContentContext | |||
|
|||
> **Deprecated** |
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.
@ryanwelcher, it looks like we still show deprecated APIs in documentation because the @wordpress/docgen
tool doesn't skip them.
Added the Needs Dev Note label in case this needs a dev note (either individual or as part of a "misc" dev note) for WP 6.1 release. |
It could get mentioned as one sentence in a bigger dev note, but I don't expect this API is important from the extenders' perspective. |
What?
withBlockContentContext
is no longer used as of #26031.Why?
__unstableGetInnerBlocksProps
go introduced in@wordpress/blocks
to fulfill the same role aswithBlockContentContext
played in the past.How?
We keep the public API and return the same component. If it is used, it will show the deprecation message on the Browser Console.