feat: naive Factory implementation for getting rid of lambdas

[ShahriyarR]

Description:

When I was trying to add DAOs as a dependency, Inject requires the lambda or partial as described here:

dependencies={
            "user_dao": Inject(lambda: UserDAO()),
            "article_dao": Inject(lambda: ArticleDAO()),
            "post_dao": Inject(lambda: PostDAO()),
        },

Implemented naive, but yet clean wrapper called Factory to inject as:

dependencies={
           "user_dao": Inject(Factory(UserDAO)),
           "article_dao": Inject(Factory(ArticleDAO)),
           "post_dao": Inject(Factory(PostDAO)),
       },

For now, it only supports variable arguments(*args)

Mostly inspired by:
https://python-dependency-injector.ets-labs.org/providers/factory.html

Information:

• All tests are passed in the local run
• Added more parameters to the original existing parametrized tests

In the future possible TODOs:

• Add **kwargs support
• Add dynamic argument additions such as: obj = Factory(UserDAO); obj.add_args(*args)

[tarsil]

@ShahriyarR this idea looks very interesting and indeed what we have discussed. Do you think you are able to also update the docs for this with examples and how tos?

[ShahriyarR]

@tarsil yes, I will add docs as well. I also need to add more tests for checking Route Level DI or Handler Level, I am still not sure how we call it :)

[tarsil]

@tarsil yes, I will add docs as well. I also need to add more tests for checking Route Level DI or Handler Level, I am still not sure how we call it :)

So, we have dependencies from the Esmerald instance down to handler (get, post, put....). So that means, Esmerald, Include, Gateway/WebSocketGateway and the handlers in general 🙂

You can see that also in the Esmerald tests 👍🏼

[tarsil]

The examples are actually really great and simple to understand. Apologies for the comments in the documentation but it is more to be consistent with the way we try to provide the "guide" through those same docs. As mentioned before, it is more like a story telling but with structure :)

[tarsil]

shouldn't this be:

self.__args: Tuple[Any, ...] = args

?

[ShahriyarR]

This can be done directly, but personally I prefer to use the getter and setter way of dealing with internal objects:

        self.__args: Tuple[Any, ...] = ()
        self.set_args(*args)

[tarsil]

Looks good to me 👍🏼 . Good stuff @ShahriyarR . We can grow this functionality even further