Community driven integrations

[Tishka17]

It is a bit hard to maintain all integrations in one place, so the idea is to extract them as external libraries.

The question is what else we need to unify base integration logic?

[Tishka17]

I guess #237 is related

[Tishka17]

The idea:

• reagento hosts template repo for dishka integrations
• any user can clone it and renaming package start doing new integration with pre-built pipeline for CI
• the user can publish it to a pypi with a name like dishka-smth
• we add a link to a project into dishka documentation so it will be visible for all users

[prepin]

Questions I can think of now are:

• Do external package needs to keep same namespace structure as parent project (dishka.integrations.smthng)?
• Should it host own documentation on separate readthedocs page or it should be available in main repo?
• Which versions of Dishka considered "supported". Do you expect integration to be tested only on recent release or it should also check 1.3, 1.2, etc?

[Tishka17]

1. No need for that. Moreover, dishka is not ready for that - we want users to do from dishka import Provider
2. I guess README is enough for that. In main repo thre will be a link.
3. Let's test on 2 version: some minimal (we have issues so just select one you are sure is ok) and "latest" (to be sure no new bugs were introduced)

[prepin]

Ok, I've prepared and published separate package

• https://pypi.org/project/dishka-rq/
• https://github.com/prepin/dishka-rq

What are next steps?

[Tishka17]

Thank you, I think that's it.

I see you do not have CI pipelines configured. I'd re commend having two of them: one for PRs for specific versions of rq, another is periodical (we run it daily) for latest versions if libraries.

We will add a link to your library into docs

[prepin]

Great, thank you!