DI Implementation

[JustSteveKing]

Now that we have a DI container, we can start to look at replacing the static arrays that we have to improve the experience.

However this starts to open up a new line of questioning. Should we look at caching information about the app?

In project applications, the config will be stored in /path/to/project/.minicli and if it is a global install then we can store it under /$_PROFILE/.minicli

[JustSteveKing]

@erikaheidi @WendellAdriel do you have any thoughts on the above with the configuration? I think it would 100% help with performance when using a DI container and will limit our requirement to use reflection so heavily.

[WendellAdriel]

I think that's a good approach to boost the performance.

[erikaheidi]

Sounds good to me! Kind of how Laravel does it, right? Config folder with .php config files that can be grouped by subject and merged into one config?