Block Bindings: Remove fallback for context.postType in post meta
#67345
+2
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SantosGuillamot
added
[Type] Code Quality
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
6 tasks
|
Size Change: -12 B (0%) Total Size: 1.82 MB
ℹ️ View Unchanged
|
cbravobernal
deleted the
update/remove-fallback-in-post-meta-post-type
branch
michalczaplinski
pushed a commit
that referenced
this pull request
Dec 5, 2024
Co-authored-by: SantosGuillamot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Remove an unnecessary fallback for
postTypein post meta block bindings source.Why?
It can just be assumed that if the
postTypeis not defined, the custom fields are not available. If I am not mistaken, this was needed before this other pull request but is not needed anymore.How?
Just removing the fallback.
Testing Instructions
e2e tests should pass and everything should work as before.
show_in_restset to true.pagestemplate.