Added option resolvers for Constructor params and additional options

[rantonmattei]

2 resolver classes, they both use a reflected object (see Reflection)

• constructor params: we figure out all constructor params i.e. which are required, which have default values, etc. and configure a Symfony OptionsResolver object
• extra params: those would be anything that is not identified as a constructor param (from the config file). To consider any of those as valid and defined, we follow those 3 3 simple rules:
  • is there a method matching that params name?
  • is there a public member matching that param name
  • is there a custom handler function set up to handle that param (those handlers would be set up in a loader object passed in)

Those 2 essentially do the same thing:

1. define valid options from a given class
2. validate them against passed in params (see theresolve method)

Constructor params are must have, you need those to instantiate a logger handler (StreamHandler for instance). Extra params is a way to consume more params for the config if needed. Let's say you want to use a handler but not all the params you want to use can be passed through the constructor LogglyHandler for instance. It takes only the token and the level... but let's say you'd like configure tags as well. The way you would typically do it is instantiate your handler first and then call either the setTag or addTag method.

Cascade allows you to do this automatically by passing add_tag as a param so everything is configured in one step

@mortaliorchard @OrCharles

[rantonmattei]

ClassLoader is missing. The test cannot mock that class. It is used as a DI. Will add it in a few...

[OrCharles]

ah, makes sense.. I was wondering what $classLoader->canHandle(.. was doing

[mortaliorchard]

This is quite simple – and clean. No major feedback here. R+

[OrCharles]

R+ once the build passes