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
Product_types is the key to do cross tasks communication, now most tasks just use a text constant which not a proper way to enforce or discover the product_types. In my mind, product_types is in the same category as mime, http headers, which helps if we have a global place for the standard ones, and also leaves some slots for customization.
Not sure whether it is overkill though :)
The text was updated successfully, but these errors were encountered:
FWIW: A few of us are working on implementing an alternative to the existing ("v1") Task API. Over the next few quarters, we hope to port a portion of the python pipeline to a v2@rule UX. See the document linked from #5440
Product_types is the key to do cross tasks communication, now most tasks just use a text constant which not a proper way to enforce or discover the product_types. In my mind, product_types is in the same category as mime, http headers, which helps if we have a global place for the standard ones, and also leaves some slots for customization.
Not sure whether it is overkill though :)
The text was updated successfully, but these errors were encountered: