-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
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
opr
force-pushed
the
fix/eslint-errors-no-disable
branch
from
November 30, 2021 14:51
2139d07
to
59e7c64
Compare
opr
requested review from
adamsilverstein,
adamziel,
ajitbohra,
cameronvoell,
dmsnell,
draganescu,
ellatrix,
getdave,
guarani,
gziolo,
kevin940726,
mkevins,
mmtr,
nerrad,
noahtallen,
noisysocks,
ntwb,
oandregal,
swissspidy,
talldan and
tellthemachines
as code owners
November 30, 2021 14:59
opr
changed the title
Fix @wordpress/comment-case ESlint errors but without adding the disable-rule pragma
Fix Nov 30, 2021
@wordpress/comment-case
ESlint errors but without adding the disable-rule pragma
opr
force-pushed
the
fix/eslint-errors-no-disable
branch
from
February 25, 2022 13:32
3d44583
to
a16e0ac
Compare
gziolo
approved these changes
Feb 25, 2022
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.
This looks great. I'm excited that we can finally land this PR. Great work @opr! 👏🏻
Open
7 tasks
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.
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:
*.native.js
files for terms that need renaming or removal).