Launch Plans launched in the UI seem to silently ignore "default_inputs" that are structs when specified in Python. So e.g.

@dataclass_json
@dataclass
class MyStruct
   foo: str
   bar: str = 'baz'

def workflow(s: MyStruct):
   pass

qux = LaunchPlan(workflow, default_inputs=dict(s=MyStruct(foo='baz', bar='qux')))

If i go to launch

workflow

with the

qux

launch plan it instead takes the default values from the struct definition. So

foo

will be unset and

bar

will be set by default as

baz

Not sure where the error is here, though. Has anyone else seen this?

This might be because of the jsonschema that has field defaults. I think this is a bug in the Ui. The backend will do the right thing. Cc @Jason Porter / @Niels Bantilan

Indeed if I go to LaunchPlan details page the struct is visible under "default inputs", but the value is listed as a "scalar", with no additional details

Aaha, if you try Flyte remote or cli it should work

yeah there are a couple of issues with dataclasses in the UI: @Eli Bixby would you mind opening up a [flyte-bug] issue? 👇

🐞 Create a new Flyte Bug issue: https://github.com/flyteorg/flyte/issues/new?assignees=&labels=bug%2Cuntriaged&template=bug_report.yaml&title=%5BBUG%5D+

I appears that Enums inside of dataclasses are also broken when specified through the UI? It's trying to convert the name of the enum rather than the value of the enum back, and getting a disallowed value error.

So the Ui works by extracting the json schema from the dataclass

So if I specify a dataclass as:

class MyEnum(enum.Enum):
   ONE = 'one'
   TWO = 'two'

class MyStruct:
    option: MyEnum

It will nicely generate a dropdown bar in the UI when I go to launch. But then if I actually run the workflow that recieves MyStruct I'll get:

ONE is not a valid MyEnum, please select one of ['one', 'two']

thanks!