-
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
Default pattern terminology to Pattern instead of Block Pattern #54708
base: trunk
Are you sure you want to change the base?
Conversation
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @foosantos! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
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!
In order to merge this PR, could you rebase with the latest trunk just to be sure? If the GitHub Action fails, you'll probably need to fix that too. thank you! |
What?
This PR replaces mentions of "Block Patterns" with "Patterns" only.
Fixes #49617.
Why?
There's an inconsistency in the labeling of the Patterns — sometimes it's "Pattern" while sometimes it's "Block Patterns" — and the goal would be to fix that.
How?
I mostly searched for the mentions of "Block Patterns" and replaced them manually based on the context.
Testing Instructions
Basically, a good step would be to search for mentions of patterns in the code and see if makes sense for these contexts.