-
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
Fix Post Content block regression #32693
Conversation
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.
Thanks! I can't believe how this was slipped - I'm sorry
Size Change: -2 B (0%) Total Size: 1.04 MB
ℹ️ View Unchanged
|
looks like the performance test is still failing, not sure if there's something else going on here. |
@@ -189,6 +189,7 @@ function* loadPostTypeEntities() { | |||
record?.title || | |||
( isTemplate ? startCase( record.slug ) : String( record.id ) ), | |||
__unstablePrePersist: isTemplate ? undefined : prePersistPostType, | |||
__unstable_rest_base: postType.rest_base, |
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.
Ideally this should be something that is available in all entities (and not just post one) but also ideally, it could potentially be better though, basically we need this properly to match with the "permissions" array, we could have a canEdit
function per entity or a getResource
or something like that. But this will do for now.
I expect the performance test to still fail in this PR because it compares against trunk which is broken now, so I'll force merge this one. |
The block has been refactored recently but it looks like the context values where not consumed properly when the block is editable.