You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm copy-pasting (through templating) the same duties in every project. To reduce boilerplate (and noise in template updates), I imagine allowing collections of duties to be loaded from entrypoints.
Describe the solution you'd like
Allow discovering and loading duties from entrypoints. A published package exposes a module containing duties, and registers a "duty" entrypoint pointing to it. When running, duty can discover that module (through stdlib's entrypoint mechanisms) and load its duties, making them available to the final user. In the end, users can install packages to be able to run duties they provide.
Describe alternatives you've considered
/
Additional context
See how that would integrate with auto-docs of duties (like in Griffe).
This could also mean a come-back of the "fulfill" project.
This issue was labeled with the fund label. The following section is automatically added by Polar.
Is your feature request related to a problem? Please describe.
I'm copy-pasting (through templating) the same duties in every project. To reduce boilerplate (and noise in template updates), I imagine allowing collections of duties to be loaded from entrypoints.
Describe the solution you'd like
Allow discovering and loading duties from entrypoints. A published package exposes a module containing duties, and registers a "duty" entrypoint pointing to it. When running, duty can discover that module (through stdlib's entrypoint mechanisms) and load its duties, making them available to the final user. In the end, users can install packages to be able to run duties they provide.
Describe alternatives you've considered
/
Additional context
See how that would integrate with auto-docs of duties (like in Griffe).
This could also mean a come-back of the "fulfill" project.
This issue was labeled with the
fund
label. The following section is automatically added by Polar.Boost priority in our backlog through Polar's "issue funding". Issues linked to monthly sponsorships of $50 or more (author, upvoters) are already prioritized, see how we manage our backlog.
The text was updated successfully, but these errors were encountered: