The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

QQ - I made a `@job` with an optional parameter with a default set to `None`, but the `dagit` UI expects this parameter to be specified (on version `0.14.5` - is this expected?

If this is for an op config schema I think <https://docs.dagster.io/_apidocs/config#dagster.Noneable|Noneable> should work

The job definition can't infer that? We're not using config schema types and we're just letting Dagster infer them.

are you using
```config_schema={'param': Optional[str]}```
? Not sure if that works.

Is this optional parameter being specified via function parameters? A la
```@job
def the_job(x=None):
    ...```

If so, right now the default value is being silently ignored. However, there's likely a path forward to getting this working as you would expect (the kwarg value being used as a default input value on the job), so going to file an issue here: <https://github.com/dagster-io/dagster/issues/8658>