Closed ljqx closed 8 years ago
Hi @ljqx, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
It looks like you're a Microsoft contributor (Zhibin Liu). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.
TTYL, MSBOT;
Hi @ljqx, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
It looks like you're a Microsoft contributor (Zhibin Liu). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.
TTYL, MSBOT;
@ljqx Thanks for your great help! I merged the request and opted for removing the 'includes' functionality to be closer to the default behavior of jshint.
Sometimes we want to include/exclude specific files to be linted. It's boring that there are lint error message for the files we don't want them to be linted.
This change contributes 2 more vscode configurations:
jshint.include
andjshint.exclude
. These 2 configurations have same structure asfiles.exclude
andsearch.exclude
, use glob pattern to match files. (See Glob for node.js). Only files match one ofjshint.include
and none ofjshint.exclude
would be linted.jshint.include
default to be{ "**/*": true }
, andjshint.exclude
default to be{}
. Which makes no break changes for users.This change partly resolve #10 for language javascript/javascriptreact. User can set
jshint.include
to be{ "**/*.es6": true, "**/*.jsx": true }
to lint only .es6 and .jsx files.