From 04ae92a2c03c5115b7b5be63ab2d03ef5c78bccd Mon Sep 17 00:00:00 2001 From: Mark Stacey Date: Mon, 15 Jul 2019 11:03:22 -0300 Subject: 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. --- development/states/send.json | 1 - 1 file changed, 1 deletion(-) (limited to 'development/states/send.json') diff --git a/development/states/send.json b/development/states/send.json index c71516edc..0dfcca1c4 100644 --- a/development/states/send.json +++ b/development/states/send.json @@ -23,7 +23,6 @@ }, "assetImages": {}, "unapprovedTxs": {}, - "currentCurrency": "USD", "conversionRate": 16.88200327, "conversionDate": 1489013762, "noActiveNotices": true, -- cgit