Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provide a lint tool #64

Open
missinglink opened this issue Aug 22, 2017 · 1 comment
Open

provide a lint tool #64

missinglink opened this issue Aug 22, 2017 · 1 comment
Labels

Comments

@missinglink
Copy link
Member

I've seen users post their pelias.json file in comments and there are fields I've never heard of before, also some settings can be old an deprecated.

We could ship a 'lint tool' as part of this repo which would scan the users local pelias.json and alert the user of errors, warnings etc.

We could then advise users to run the linter periodically to ensure their config is up-to-date and valid.

@trescube
Copy link
Contributor

Isn't this what the schema does the basis of? The API doesn't currently cover the entire config, but running npm run config will display the config and any errors it encounters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants