[Feature] - Allow importing the object from string in the factory

[tarsil]

Checklist

• The code has 100% test coverage
• The documentation was properly created or updated (if applicable) following the correct guidelines and language.
• You branch out from the V2 tag and the V2 tag was properly rebased from main.

@ShahriyarR, today I was using this amazing new feature and I came across an idea to apply on the top of this and grow your initial functionality. Allowing to pass a string <module>.<object> type and delegate the import to the Factory itself. This way we can also avoid importing a lot of objects on the top of each needed file.

I ran a PoC and added some tests for you to see what I mean. In the end, it is adding an extra alternative on the top of the already existing functionality.

Something like this:

from esmerald import Factory, Include, Inject

route_patterns = [
    Include(
        "/api/v1",
        routes=[
            Include("/accounts", namespace="accounts.v1.urls"),
            Include("/articles", namespace="articles.v1.urls"),
            Include("/posts", namespace="posts.v1.urls"),
        ],
        interceptors=[LoggingInterceptor],  # Custom interceptor
        dependencies={
            "user_dao": Inject(Factory("myapp.accounts.daos.UserDAO")),
            "article_dao": Inject(Factory("myapp.articles.daos.ArticleDAO")),
            "post_dao": Inject(Factory("myapp.posts.daos.PostDAO")),
        },
    )
]

What do you think? Your idea for the factory was game changing here and I'm already using it.
@PeterChain what do you think about this too?

[ShahriyarR]

I really like the idea, quite clean and neat ) I need to take a look at implementation, but the idea is powerful.

It can be further improved to have something called "automated wiring" to wire up dependencies and dependants.
Say we have defined the dependency as "user_dao": Inject(Factory("myapp.accounts.daos.UserDAO")),

And some other modules wait for this dependency.
You define your wirings(dependants):

dependencies={
            "user_dao": Inject(Factory("myapp.accounts.daos.UserDAO")),
            "article_dao": Inject(Factory("myapp.articles.daos.ArticleDAO")),
            "post_dao": Inject(Factory("myapp.posts.daos.PostDAO")),
        },
        
   wired = {
   "modules": ["myapp.accounts.views", "myapp.users.views"],
   "packages": ["somepackage"]
   }

Now in the "myapp.accounts.views" if you use something like global Provider: Provide["user_dao"] it will take it from dependencies and use, it again without any imports. But maybe we have already this idea in place.

[tarsil]

Is the wired also on every level? Hm, I would need some more details on this with more precise examples as I'm not entirely sure if I'm understanding. Maybe this is for another PR specifically?

[ShahriyarR]

Definitely, another PR will be a much better fit here.
For this PR, it looks awesome)

[tarsil]

Definitely, another PR will be a much better fit here. For this PR, it looks awesome)

Perfect! We can even open a discussion and go from there. Debate on this possibility. I would like to know and understand more. In the meantime, I will be merging this one.