Validate configuration

[lencioni]

It would be nice if I saw a warning if my configuration file contained a key that Import-JS doesn't know about. Even better if it would validate some or all of the values.

I think that this would help people who have misconfigured something, but also would help people who have too new of configuration or too new of a plugin for the configuration (a possible solution to some issues we discussed in #153).

[lencioni]

This looks useful: https://github.com/ruby-json-schema/json-schema

[trotzig]

I've thought about this too. It's important that we find a way that is helpful without being too strict. Validation is likely to tie the configuration file to a certain version of the plugin, which might not always be a good thing. That being said, if we implement it the right way it should help out in the situations you listed above.

[mikabytes]

Do I understand it correctly that what remains on this issue is to validate the values of correct fields?

I've used Yup (joi) for schema validation for APIs in the past. I could give this a go if needed.

[lencioni]

Do I understand it correctly that what remains on this issue is to validate the values of correct fields?

That sounds about right

I've used Yup (joi) for schema validation for APIs in the past. I could give this a go if needed.

I'm not familiar with yup or joi, but have used json schema with ajv in the past and that has worked well for me. Also, I found this benchmark that makes it seem that yup and joi are quite slow in comparison, FWIW: https://github.com/icebob/validator-benchmark

What do you think about ajv and a json schema?

[mikabytes]

Woah, 43 times faster is a compelling argument. Good suggestion. I will give it a go!