Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we manage product_types in a global space? #6238

Closed
shuoli84 opened this issue Jul 26, 2018 · 2 comments
Closed

Should we manage product_types in a global space? #6238

shuoli84 opened this issue Jul 26, 2018 · 2 comments

Comments

@shuoli84
Copy link
Contributor

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 :)

@stuhood
Copy link
Member

stuhood commented Jul 26, 2018

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

@stuhood
Copy link
Member

stuhood commented Apr 12, 2019

Closing this one as answered.

@stuhood stuhood closed this as completed Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants