Remove container resolving

[josephmancuso]

This PR that will remove resolving via parameter and only support annotations 😢
I actually kept the possibility to resolve parameters but it's disabled by default. You can potentially enable it on a per project basis via something like this in your wsgi.py file:

app = App(resolve_parameters=True)

but it's disabled by default and all Masonite packages and core will only use annotations

[coveralls]

Coverage increased (+0.6%) to 92.006% when pulling ba30290 on remove-container-resolving into d189e65 on develop.

[vaibhavmule]

What was the reason to remove container resolving?

[josephmancuso]

is not particularly "removed". It is disabled by default now. You can enable it on a per application basis.

The reasoning was that as there becomes more and more packages being developed, simply using a simple namespace like Logger can be overridden by other packages. This means when building a package you have to think about all the conflicting binding names.

Some packages have the ability to override other packages by simply overriding the name in the container.

[josephmancuso]

in 2.1 and possibly 2.2, the correct way to bind things will likely be doing something like:

app.simple(Class())

which binds into the container using the class name, which there should only ever be one class of the same type at a time

[vaibhavmule]

Thanks for information.

Make sense.