-
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
Code quality: Fix typos #67304
base: trunk
Are you sure you want to change the base?
Code quality: Fix typos #67304
Conversation
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. |
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @szepeviktor! In case you missed it, we'd love to have you join us in our Slack community. 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.
@szepeviktor Thanks for the cleanup.
I think this PR contains a lot of unnecessary changes that need to be fixed and go through all CI. Could you address these issues?
packages/block-editor/src/components/global-styles/filters-panel.js
Outdated
Show resolved
Hide resolved
packages/components/src/surface/test/__snapshots__/index.tsx.snap
Outdated
Show resolved
Hide resolved
...ste-should-cut-partial-selection-and-merge-like-a-normal-delete---not-forward-2-chromium.txt
Outdated
Show resolved
Hide resolved
...d-paste-plain-text-in-plain-text-context-when-cross-block-selection-is-copied-2-chromium.txt
Outdated
Show resolved
Hide resolved
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.
I'd recommend to severely limit the scope of this PR. It's very hard to review and approve 436 typos across 259 files. As previously noted, many of the "typos" are not really typos here at all.
How about starting with just the typos in markdown files and code comments?
This is a good idea. A) I could close this PR and provide you with my Typos configuration Please decide! |
I've done all I could. |
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 for the update. I have left additional feedback.
Could you resolve the lint errors first to ensure it passes all CI? If you run npm run lint:js:fix
, all lint errors will be resolved.
docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md
Outdated
Show resolved
Hide resolved
docs/reference-guides/interactivity-api/core-concepts/using-typescript.md
Outdated
Show resolved
Hide resolved
packages/react-native-bridge/android/react-native-bridge/build.gradle
Outdated
Show resolved
Hide resolved
I've done all I could. |
All right. One last commit. |
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.
Thank you for all the effort here.
I would echo the comments of some other reviewers that it would be preferable to break this out into separate PRs for:
- Markdown
- Code comments
- Code changes (e.g variable renaming...etc)
That would:
- Make it easier to review
- Easier to revert in case of Issue.
When reviewing 256 files for changes it's easy to miss how a given change might impact the file as a whole.
I'd certainly feel a lot more comfortable if it was possible.
Hello Dave! The thing is this PR is a We need someone who can cherrypick files for your three categories. |
... maybe an LLM |
docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md
Outdated
Show resolved
Hide resolved
…to undestanding-global-state-local-context-and-derived-state.md
@t-hamano, I addressed your feedback related to the slug change for the developer documentation page. I also rebased the PR with the latest changes from
Yes, all of the issues are reported because of differences with how Prettier formats code. By the way, it would be cool to have GitHub integration that can be triggered with the label to automatically fix such issues. @szepeviktor, that a cool usage of the tool. Very impressive given the complexity of the Gutenberg codebase. Thank you for working on this PR. |
docs/reference-guides/interactivity-api/core-concepts/using-typescript.md
Outdated
Show resolved
Hide resolved
packages/block-editor/src/components/text-transform-control/README.md
Outdated
Show resolved
Hide resolved
@@ -3417,7 +3417,7 @@ protected static function should_override_preset( $theme_json, $path, $override | |||
|
|||
/** | |||
* Returns the default slugs for all the presets in an associative array | |||
* whose keys are the preset paths and the leafs is the list of slugs. | |||
* whose keys are the preset paths and the leaves is the list of slugs. |
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.
Note: This typo is already fixed in the core, so a backport changelog should not be necessary.
@gziolo Thanks for the fix. I've checked all the files again and we should be able to ship this PR.
What would it take to get the Static Analysis CI to pass? I checked out this branch and opened the file that is causing the lint error, but my code editor doesn't give any warnings 🤔 |
What?
Found few years of typos.
How?
Would you like me to work on it?
https://github.com/crate-ci/typos