Mark Stacey 04ae92a2c0 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 11:03:22 -03:00
..
account-detail-with-shapeshift-tx.json
account-detail-with-transaction-history.json
account-detail.json
account-list-with-imported.json
accounts-loose.json
accounts.json
add-token.json
compilation-bug.json
conf-tx.json
config.json
confirm-new-ui.json
confirm-sig-requests.json
create-vault-password.json
currency-localization.json
custom-rpc.json
empty-account-detail.json
first-time.json
help.json
import-private-key-warning.json
import-private-key.json
locked.json
lost-accounts.json
navigate-txs.json
new-account.json
new-vault.json
notice.json
pending-crash.json
pending-signature.json
pending-tx-insufficient.json
pending-tx.json
personal-sign.json
private-key-export-success.json
private-key-export.json
private-network.json
restore-vault.json
send-edit.json
send-new-ui.json
send.json
shapeshift.json
show-seed-words.json
terms-and-conditions.json
tx-list-items.json