Inject possible dependencies in codec and validator

[bburnichon]

Make it possible to configure options on validators used

[webmozart]

Hi @bburnichon, thank you for this PR! :) What's the use case for this change?

[bburnichon]

I have a silex project where I need to configure specific validation for each encoding/decoding. This way, library is fully decoupled and I can have a configured JsonDecoder/JsonEncoder in Pimple container for each use case.

Also, I already have a JsonSchema\UriRetriever in my container and want to use it for all validations to minimize Http roundtrips. I inject my UriRetriever in $validatorFactory:

$app['json-schema.retriever'] = $app->share(function () {
  return new UriRetriever();
});
$app['json-schema.validator_factory'] = $app->protect(function () use ($app) {
  return new Validator($app['json-schema.url_retriever']);
});

$app['json.validator'] = $app->share(function (Application $app) {
  return new JsonValidator($app['json-schema.validator_factory']);
});

$app['json.decoder'] = $app->share(function (Application $app) {
  return new JsonDecoder($app['json.validator']);
});

[webmozart]

Why do you need support for callables in here instead of directly injecting the Validator?

[bburnichon]

Because a new instance of Validator should be used at each call to check.

[webmozart]

Why don't you simply reset() the validator before using it?

[webmozart]

(which, of course, I could have done too :) )

[bburnichon]

Because I did not knew it exists! ;)

[bburnichon]

This PR includes all changes from #9.

@webmozart I can squash commits if you prefer to keep a clean history.

[webmozart]

Thanks for updating! :) I don't think this needs to live in a separate method. You can simply inline the reset() call above.

[webmozart]

No, looks good :) Thanks a lot @bburnichon!