This is a fork from linter-js-standard, but specifically for the team I work with and designed to work with just the js standard style.
apm install linter-js-tenx
standard
style.standard
style, and some of them are not.standard
parser npm install
ed within a project. Allows different projects to use their own version of the standard
linter when you don't want to use the one included with this plugin.package.json
:
standard
configuration).Lint markdown fenced code blocks.
Only lint if the project has opted in to js-standard
by declaring standard as (1) a dependency in dependencies
or devDependencies
, or (2) declaring a top-level standard
config block. Allows this plugin to exist along with other linter plugins and be off by default.
Note: This will opt for the package.json
located in the project folder.
If the parent project includes standard
in dependencies
or devDependencies
, and it is npm install
ed in the project node_modules
, then use that version from the project. If not npm install
ed, the plugin will log a warning to the atom console (should you wish to debug if the lint errors you are getting are unexpected) and will use the one included in this plugin.
Enable/disable showing the id of the offended eslint rules.
package.json
The plugin will respect an extended standard
configuration object located inside of your project's package.json
file.
To have the linter not warn about undeclared variables when using global variables, add a globals
section to package.json:
{"standard": {"globals": ["var1","var2"]}}
Custom parsers currently supported:
To use a custom parser, extend the standard
object in your package.json
file:
{"standard": {"parser": "esprima"}}
To opt to ignore files from linting, extend the standard
object in your package.json
file with a single glob expression:
{"standard": {"ignore": "*.spec.js"}}
or an array of glob expressions:
{"standard": {"ignore": ["*.spec.js", "*.legacy.js"]}}
If the file open in the editor would have normally been linted, but the file path matches one of the glob patterns, it will not be linted.
See: https://github.com/isaacs/minimatch
MIT
This is the second atom plugin that I've worked on and have decided to make rubber duck coding notes to myself. I may remove these notes over time, but for now I'm leaving them here for myself and anyone who may want them.
My dev procedure for working on this plugin:
# These commands are mac-centric, but could be tweaked for other systems# Link this plugin to my atom app, run inside this directoryatom link# Launch atom in dev mode (from terminal)atom -d# When in dev mode and I've made changes to the package, restart atom to# recognize the changesctrl-opt-cmd-L
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.