Skip to content
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 @wordpress/comment-case ESlint errors but without adding the disable-rule pragma #37006

Merged
merged 67 commits into from
Feb 25, 2022

Conversation

opr
Copy link
Contributor

@opr opr commented Nov 30, 2021

Description

This PR is a cleanup of code comments that don't conform to the new @wordpress/comment-case rule.

It is Related to #36866 but the comments such as eslint-disable-next-line etc. are removed.

How has this been tested?

It is based off #36866 and I manually inspected every file there, this PR just removes the comments that disable the ESLint rule, I didn't test all of the other files.

Types of changes

This PR only changes comments, no functionality would be affected.

Checklist:

  • My code is tested.
  • My code follows the WordPress code style.
  • My code follows the accessibility standards.
  • I've tested my changes with keyboard and screen readers.
  • My code has proper inline documentation.
  • I've included developer documentation if appropriate.
  • I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).

@opr opr force-pushed the fix/eslint-errors-no-disable branch from 2139d07 to 59e7c64 Compare November 30, 2021 14:51
@opr opr marked this pull request as ready for review November 30, 2021 14:59
@opr opr changed the title Fix @wordpress/comment-case ESlint errors but without adding the disable-rule pragma Fix @wordpress/comment-case ESlint errors but without adding the disable-rule pragma Nov 30, 2021
@gziolo gziolo added the [Type] Code Quality Issues or PRs that relate to code quality label Nov 30, 2021
@gziolo
Copy link
Member

gziolo commented Nov 30, 2021

There is one failing JS unit test:

Screenshot 2021-11-30 at 16 30 01

I bet it's caused by the changes in the source file used in the test fixture. It's probably enough to regenerate the test snapshot.

@opr opr force-pushed the fix/eslint-errors-no-disable branch from 3d44583 to a16e0ac Compare February 25, 2022 13:32
Copy link
Member

@gziolo gziolo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. I'm excited that we can finally land this PR. Great work @opr! 👏🏻

.eslintrc.js Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Code Quality Issues or PRs that relate to code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants