eslint-plugin-i18n-json
eslint-plugin-i18n-json copied to clipboard
godaddy
Fully extendable eslint plugin for JSON i18n translation files.
Hello, Can you upgrade and publish a new version to fix a security issue ? Seems nomnom is no longer supported and maintained Regards
Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project. #### Changes included in this PR - Changes to the following...
This library has a high severity dependency (underscore 1.6.0). ``` └─┬ [email protected] └─┬ [email protected] └─┬ [email protected] └── [email protected] ``` I did some digging. `nomnom` has been deprecated and `jsonlint` has...
**Problem** When installing _eslint-plugin-i18n-json_ with jspm, the following warning is displayed ` warn (jspm) Deprecation warning for npm:[email protected]: backwards incompatible, please upgrade to 6.0 instead ` This causes jspm being...
Currently it is hardcoded that Arrays can't be a valid translation. However, based on the setup, there are some legitimate usages of Arrays and this is blocking it for no...
- This PR adds a new rule `i18n-json\identical-placeholders` to help validate the placeholders / variables used in the translations. - A translator who is not very much familiar with the...
When multiple files with the same suffix matching another language file are included in the filePaths there is an issue matching the correct file to check. I updated the [example/multiple-files-per-locale...
Please consider adding a rule that warns/disallows a key to be used more than once in the JSON.
``` "login-form": { "login": "login", "logout": "logout" } ``` How i can validate `login-form` name as well as `login` and `logout` keys with custom-syntax-validator?
