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
I am more or less re-opening this issue. If I understand the above line of code correctly, there currently exists no way to set the name of the condition branches field in a conditional task group.
Not that I can find. Happy to be wrong here, but it looks like this field will always be none. I think if the aforementioned line was changed from name=None to name=name this would sort things out. Not entirely sure what that would look like. Another option would be to add a method to set the name for the ConditionBranches.
Obviously, this is pretty nit picky, but the readability bothers me. Thank you for taking a look, and I apologize if this is already fixed in some way that I haven't found yet.
The text was updated successfully, but these errors were encountered:
Feature Area
/area backend
pipelines/sdk/python/kfp/dsl/tasks_group.py
Line 167 in 60a8865
What is the use case or pain point?
I am more or less re-opening this issue. If I understand the above line of code correctly, there currently exists no way to set the name of the condition branches field in a conditional task group.
What feature would you like to see?
Able to set a custom name for a ConditionBranches task group.
Is there a workaround currently?
Not that I can find. Happy to be wrong here, but it looks like this field will always be none. I think if the aforementioned line was changed from
name=None
toname=name
this would sort things out. Not entirely sure what that would look like. Another option would be to add a method to set the name for the ConditionBranches.Obviously, this is pretty nit picky, but the readability bothers me. Thank you for taking a look, and I apologize if this is already fixed in some way that I haven't found yet.
The text was updated successfully, but these errors were encountered: