Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Makes cover block dynamic and adds featured image binding #39658
Makes cover block dynamic and adds featured image binding #39658
Changes from all commits
c6952d9
a8b419c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
useEntityProp
only returns a value if the post is already loaded. It's true for the post editor, but can this be used outside of it? Would it break if the post is still being loaded? Or would this block not even be displayed because there is no post content to render? Either way, the future me reading this code would love to find a tiny comment that makes the constraint explicit.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.
Indeed, if there's no post in the context (which can happen in a lot of places, for instance a "category" template), we should probably remove the "use featured image" all together.
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.
Interesting, normally
featuredImage
can be undefined and if "use featured image" is toggled in a non post context nothing happens. The disabling of the feature cannot be b/c offeaturedImage
value, we need to know inside the cover block if the surrounding "thing" will eventually be able to provide a featured image. Not sure if this is possible yet. I think checking template inside the block type is quite a coupling effect.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.
We should be checking the "post" in the context IMO. We should have a post type that supports featured images