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
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 base taskiq 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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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