Configuration overhaul

[dbrumann]

• Clarifies and introduces intended extension points (still experimental and work in progress!)
• Changes namespaces and class names:
  • AstRunner > Ast
  • Collector > Layer\Collector
  • DependencyEmitter > Dependency\Emitter
  • RulesetEngine -> Result
  • Events are moved into a shared directory src/Event/
  • some classes were renamed and moved, e.g. file loading in Configuration is moved out into File instead
• Reduces configuration layer in favor of having the class using the config (arrays) verify and process them
• All configuration is now processed during container compilation allowing us to change how certain classes are collected and used (replace Registry with ContainerInterface).

[patrickkusebauch]

I have 2 questions that are not really clear to me about how they would be done going forward. And it might just be me not familiar with the Symfony Configuration/Container builder process:

• Would it still be possible to have configurations for multiple different formatters in the same deptac.yaml file? And the correct one will be used based on the command line parameter choosing the formatter?
• Is it still possible for multiple different formatters to use the same key in the deptac.yaml config file? Like the different GrapViz formatters do at the moment?

[dbrumann]

Would it still be possible to have configurations for multiple different formatters in the same deptac.yaml file? And the correct one will be used based on the command line parameter choosing the formatter?

Yes, you can still configure multiple formatters in the deptrac.yaml. We pick the right formatter using the FormatterProvider, much like we did before. Only that formatter will be instantiated during the analyse command all others are "dormant".

So, this should not change the behavior. For extensions this has the benefit that you can now register a custom formatter requiring configuration, without having to register the configuration file in Deptrac (e.g. like with ConfigurationGraphviz or ConfigurationCodeclimate).

Is it still possible for multiple different formatters to use the same key in the deptac.yaml config file? Like the different GrapViz formatters do at the moment?

Yes, at least that's how it is intended. The tagged_locator uses the static getName-function just like before to map a service to an alias. If you register a new service with that name, it should overwrite the existing one.