Replies: 1 comment
-
What will be the default behavior for older versions of libraries that were released before this proposal? I am confused by the following case:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, we have a short paragraph about the conventions that brokers support in the documentation.
We'd like to standardize this by introducing a
Capabilities
enum in the basetaskiq
package.I propose defining an enum for each pluggable component, including:
Broker
ResultBackend
ScheduleSource
Each component will have a
ClassVar
listing its supported capabilities. For every component, there will be a corresponding enum that defines all possible capabilities.For example:
With this approach, the library can warn users about unsupported actions, making it safer and more consistent to work with label-based capabilities.
Beta Was this translation helpful? Give feedback.
All reactions