Skip to content

Added InspectorControls import to example #45872

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Nov 21, 2022
Merged

Added InspectorControls import to example #45872

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f92b509
Added InspectorControls import to example
flexseth Nov 18, 2022
3828999
Update docs/how-to-guides/block-tutorial/extending-the-query-loop-blo…
ryanwelcher Nov 18, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/how-to-guides/block-tutorial/extending-the-query-loop-block.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,6 +192,8 @@ Notice that we have also disabled the `postType` control. When the user selects
Because our plugin uses custom attributes that we need to query, we want to add our own controls to allow the users to select those instead of the ones we have just disabled from the core inspector controls. We can do this via a [React HOC](https://reactjs.org/docs/higher-order-components.html) hooked into a [block filter](https://developer.wordpress.org/block-editor/reference-guides/filters/block-filters/), like so:

```jsx
const { InspectorControls } = wp.blockEditor;

export const withBookQueryControls = ( BlockEdit ) => ( props ) => {
// We only want to add these controls if it is our variation,
// so here we can implement a custom logic to check for that, similiar
Expand Down