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

refactor: Be more selective in eslint ignorance #5955

Merged
merged 1 commit into from
Feb 23, 2022

Conversation

cpcallen
Copy link
Contributor

The basics

  • I branched from develop
  • My pull request is against develop
  • My code follows the style guide

The details

Proposed Changes

Rather than ignoring blockly_uncompressed.js, gulpfile.js and core/utils/global.js entirely, add suitable eslint-disable directives to those files so that they lint cleanly (and migrate gulpfile.js to use const instead of var).

Behaviour Before Change

Lints cleanly.

Behavior After Change

Lints more stuff cleanly.

Reason for Changes

Catch other (future) lint in these files.

Test Coverage

npm run lint completes successfully.

Rather than ignoring blockly_uncompressed.js, gulpfile.js and
core/utils/global.js entirely, add suitable eslint-disable directives
to those files so that they lint cleanly (and migrate gulpfile to
use const instead of var).
@cpcallen cpcallen added component: build process PR: chore General chores (dependencies, typos, etc) labels Feb 23, 2022
@cpcallen cpcallen requested a review from a team as a code owner February 23, 2022 21:54
@cpcallen cpcallen merged commit 00a75ca into google:develop Feb 23, 2022
@cpcallen cpcallen deleted the less-eslint-ignorance branch February 23, 2022 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: build process PR: chore General chores (dependencies, typos, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants