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

Add prefer-const #331

Merged
merged 6 commits into from
Jan 19, 2017
Merged

Add prefer-const #331

merged 6 commits into from
Jan 19, 2017

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Jan 18, 2017

Our code style says we prefer consts, so add it to the linter.

Our code style says we prefer consts, so add it to the linter.
@richvdh
Copy link
Member

richvdh commented Jan 19, 2017

pfff. 1860 warnings is a bit much to be dealing with.

  1. Are we sure we want to enforce this rule? Even if the code style says so, I'm not necessarily sure I want to be forced into it every time.
  2. If we are, maybe we should try a --fix rather than tolerating all those warnings?

@richvdh richvdh assigned dbkr and unassigned richvdh Jan 19, 2017
@dbkr
Copy link
Member Author

dbkr commented Jan 19, 2017

I agree with it being annoying being forced into particular things, although consts can help prevent bug, so could be useful. Running --fix seems to do sensible things, so happy to add that.

@dbkr dbkr assigned richvdh and unassigned dbkr Jan 19, 2017
@@ -11,7 +11,7 @@
"build": "babel -s -d lib src && rimraf dist && mkdir dist && browserify --exclude olm browser-index.js -o dist/browser-matrix.js --ignore-missing && uglifyjs -c -m -o dist/browser-matrix.min.js dist/browser-matrix.js",
"dist": "npm run build",
"watch": "watchify --exclude olm browser-index.js -o dist/browser-matrix-dev.js -v",
"lint": "eslint --max-warnings 122 src spec",
"lint": "eslint --max-warnings 1860 src spec",
Copy link
Member

Choose a reason for hiding this comment

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

still?

@richvdh richvdh merged commit 49e6fd3 into develop Jan 19, 2017
@t3chguy t3chguy deleted the dbkr/prefer_const branch May 10, 2022 14:01
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