metamask-extension/.eslintignore

node_modules/**
dist/**
builds/**
test-builds/**
docs/**
coverage/

development/bundle.js
development/states.js

app/scripts/lib/extension-instance.js
app/scripts/chromereload.js
app/vendor/**

ui/lib/blockies.js

test/integration/bundle.js
test/integration/jquery-3.1.0.min.js
test/integration/helpers.js

package-lock.json
update eslint rules and paths 2018-07-03 00:35:30 +02:00			`node_modules/**`
			`dist/**`
			`builds/**`
Update .eslintignore 2018-07-03 21:43:14 +02:00			`test-builds/**`
update eslint rules and paths 2018-07-03 00:35:30 +02:00			`docs/**`
eslintignore: Add test coverage dir to eslintignore 2018-09-24 22:02:00 +02:00			`coverage/`
update eslint rules and paths 2018-07-03 00:35:30 +02:00
			`development/bundle.js`
			`development/states.js`

Implement some cross-browser practices (#473) * Add mozilla plugin key to manifest * Move all chrome references into platform-checking module Addresses #453 * Add chrome global back to linter blacklist * Add tests 2016-07-21 19:45:32 +02:00			`app/scripts/lib/extension-instance.js`
update eslint rules and paths 2018-07-03 00:35:30 +02:00			`app/scripts/chromereload.js`
add app/vendor dir to eslintignore 2018-08-10 05:38:01 +02:00			`app/vendor/**`
update eslint rules and paths 2018-07-03 00:35:30 +02:00
			`ui/lib/blockies.js`

Ignore tests bundle, jquery, abd helpers 2017-05-04 23:33:29 +02:00			`test/integration/bundle.js`
			`test/integration/jquery-3.1.0.min.js`
			`test/integration/helpers.js`
Lint `.json` files (#6852) We've been using the `eslint-plugin-json` plugin for some time, but we haven't been visiting `.json` files in the lint script. The lint script has now been updated to incude `.json` files, which means any invalid JSON will result in a lint error. Unfortunately this JSON plugin doesn't seem to apply the other eslint rules (such as `key-spacing`) to the JSON files. I wasn't able to find a way to get that to work. Instead I manually auto-formatted each of the locale `message.json` files, which fixed many whitespace inconsistencies. The `states.json` file was deleted completely, as it appears to be unused. It wasn't a valid JSON file anyway, it was JavaScript. It looks like a `states.js` file is automatically generated, but an old copy was accidentally saved as `states.json` and included in the repo. Many duplicate key errors were found and fixed in the `development/states/` JSON files. `package-lock.json` was added to `.eslintignore` because it was very slow to lint, and linting it doesn't provide much value. 2019-07-15 16:03:22 +02:00
			`package-lock.json`