-
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
Refactor: Reuse code of the editor placeholder across Post Comments and Post Comments Form #40560
Conversation
Size Change: -128 B (0%) Total Size: 1.23 MB
ℹ️ View Unchanged
|
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.
LGTM!
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.
Same here.
Thanks a lot @michalczaplinski! 🚀 |
While it's just a code change, it'd be nice if we could backport this for WP 6.0.1 in order to facilitate other fixes planned for the point release (i.e. fewer conflicts when applying patches etc). |
…nd Post Comments Form (#40560) * Create a separate template for the Comments Form * Use the form in the Post Comments block * Add the missing "return" in the CommentForm
I just cherry-picked this PR to the wp/6.0 branch to get it included in the next release: 7e7d6cd |
What?
Create a
CommentsForm
component that is re-used in the editor across both Post Comments and the Post Comments Form blocks.This PR has no functional changes, it's a refactoring.
Why?
This is based on suggestion by @ockham in #40484 (review)
Previously, there was a duplication of code between the Post Comments and the Post Comments Form blocks.
Testing Instructions