Config validation out of date - and not triggered

[rprieto]

The code seems to use js-match to validate the config, however:

• the schema is out of date (only checks the URL)
• we don't actually do anything if any errors are returned

Do we really need to validate the schema?
And if we do, would we just throw an exception if the config doesn't match?

[nguyenchr]

@rprieto good catch
It originally used to use json-config instead of js-match so it took care of throwing the error
I would suggest that we remove the validation altogether, I'm not sure it's needed

[rprieto]

Yep agreed, for top-level services it makes sense to validate the config, but for a testing library I'd say we can just rely on people calling it correctly.