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
Right now the user needs to know the output of a task because the only way to get it is using the getOutput("<attributeName>"). This is difficult during the development because you need to check the output class or docs to know what are the available types, also writing the name manually produces typos errors that only appear at registration time. The proposal here is to have some way to use the output class during the workflow development on that way you can access directly to the output class attributes.
Goal: What should the final outcome look like, ideally?
SumTaskOutput class
@AutoValuepublicabstractstaticclassSumOutput {
publicabstractSdkBindingData<Long> c();
publicstaticSumOutputcreate(SdkBindingData<Long> c) {
returnnewAutoValue_SumTask_SumOutput(c);
}
}
Motivation: Why do you think this is important?
Right now the user needs to know the output of a task because the only way to get it is using the
getOutput("<attributeName>")
. This is difficult during the development because you need to check the output class or docs to know what are the available types, also writing the name manually produces typos errors that only appear at registration time. The proposal here is to have some way to use the output class during the workflow development on that way you can access directly to the output class attributes.Goal: What should the final outcome look like, ideally?
SumTaskOutput class
Current status:
Desire status:
This allows the user to auto-discover the output attributes using an IDE, and also. check that you choose only available attributes at compile time.
Describe alternatives you've considered
no alternatives
Propose: Link/Inline OR Additional context
flyteorg/flytekit-java#164
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: