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

chore: Fix grunt dev:no-lint #1314

Merged
merged 4 commits into from
Jan 22, 2019
Merged

chore: Fix grunt dev:no-lint #1314

merged 4 commits into from
Jan 22, 2019

Conversation

WilcoFiers
Copy link
Contributor

@WilcoFiers WilcoFiers commented Jan 16, 2019

Small bug fix. no-lint needs to run run:npm_run_imports.

Reviewer checks

Required fields, to be filled out by PR reviewer(s)

  • Follows the commit message policy, appropriate for next version
  • Has documentation updated, a DU ticket, or requires no documentation change
  • Includes new tests, or was unnecessary
  • Code is reviewed for security by: @JKODU

@WilcoFiers WilcoFiers requested a review from jeeyyy January 16, 2019 10:51
@WilcoFiers WilcoFiers requested a review from a team as a code owner January 16, 2019 10:51
Copy link
Contributor

@jeeyyy jeeyyy left a comment

Choose a reason for hiding this comment

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

👍

@WilcoFiers WilcoFiers merged commit 2660efc into develop Jan 22, 2019
@WilcoFiers WilcoFiers deleted the no-lint-fix branch January 22, 2019 10:03
stephenmathieson added a commit that referenced this pull request Jan 30, 2019
This patch removes all of the ESLint stuff from the Grunt configuration. There have been numerous efforts to "fix" the existing Grunt/ESLint setup which all seem unnecessary. Now, if you want to lint your code, just do `npm run eslint`. If you don't want to lint your code, then don't do `npm run eslint`.

Ref: #1342, #1314, #1267, #1255, #1247, and probably others...
WilcoFiers pushed a commit that referenced this pull request Feb 1, 2019
This patch removes all of the ESLint stuff from the Grunt configuration. There have been numerous efforts to "fix" the existing Grunt/ESLint setup which all seem unnecessary. Now, if you want to lint your code, just do `npm run eslint`. If you don't want to lint your code, then don't do `npm run eslint`.

Ref: #1342, #1314, #1267, #1255, #1247, and probably others...

## Reviewer checks

**Required fields, to be filled out by PR reviewer(s)**
- [x] Follows the commit message policy, appropriate for next version
- [x] Has documentation updated, a DU ticket, or requires no documentation change
- [x] Includes new tests, or was unnecessary
- [x] Code is reviewed for security by: @WilcoFiers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants