-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Validate usable render behavior on registered block #362
Copy link
Copy link
Closed
Labels
Good First IssueAn issue that's suitable for someone looking to contribute for the first timeAn issue that's suitable for someone looking to contribute for the first time[Feature] Block APIAPI that allows to express the block paradigm.API that allows to express the block paradigm.[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] TaskIssues or PRs that have been broken down into an individual action to takeIssues or PRs that have been broken down into an individual action to take
Description
Metadata
Metadata
Assignees
Labels
Good First IssueAn issue that's suitable for someone looking to contribute for the first timeAn issue that's suitable for someone looking to contribute for the first time[Feature] Block APIAPI that allows to express the block paradigm.API that allows to express the block paradigm.[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] TaskIssues or PRs that have been broken down into an individual action to takeIssues or PRs that have been broken down into an individual action to take
Type
Fields
Give feedbackNo fields configured for issues without a type.
When registering a block, we should ensure that it has at minimum a
saveimplementation (front-end UI representation) and optionallyedit.Once validated, we can collapse logic here to return early only on
settingsbeing falsey and assume if settings exist that aeditorsavefunction/component can be used for displaying the block:https://github.com/WordPress/gutenberg/blob/15db036/editor/editor/mode/visual.js#L25-L32