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: run eslint as a part of grunt dev #1267

Merged
merged 2 commits into from
Dec 4, 2018
Merged

chore: run eslint as a part of grunt dev #1267

merged 2 commits into from
Dec 4, 2018

Conversation

jeeyyy
Copy link
Contributor

@jeeyyy jeeyyy commented Dec 4, 2018

The PR does the below:

  • adds npm run eslint as a part of grunt dev and for file changes watch.

Based on requested changes in comment - #1256 (comment)

Closes issue: NA

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: @WilcoFiers

@jeeyyy jeeyyy requested a review from a team as a code owner December 4, 2018 11:03
@jeeyyy jeeyyy changed the title chore: run eslint part of grunt dev chore: run eslint as a part of grunt dev Dec 4, 2018
@jeeyyy jeeyyy requested a review from WilcoFiers December 4, 2018 11:03
@WilcoFiers WilcoFiers merged commit 9930bb9 into develop Dec 4, 2018
@WilcoFiers WilcoFiers deleted the run-eslint branch December 4, 2018 19:17
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.

2 participants