Should

dr.visualize_execution()

reveal what possible

@config.when

arguments exist with their paths?

No. The driver is already initialized and thus configuration has already been resolved. What are you trying to show/figure out?

For a desired node, I wanted to know which possible flags are available to use with it.

So this isn’t config, this is inputs. You’ll be able to see it as an input to that node from the DAG, right? Unless

env

is not “test” (I think your logic might be reversed), in which case it won’t show up

Ok, so I shouldn't expect to see the same dependency in example (1) as example (2)? Example (1) Does not show the optional dependency `filter_src1`in DAG

@config.when(env="test")
@pipe(
    step(
        _filter_data, 
        source("filter_src1"),
    )
)
def trades__test(raw_trades: pd.DataFrame) -> pd.DataFrame:
    return raw_trades

Example (2) Shows the optional dependency

filter_src1

in DAG

@config.when(env="test")
def trades__test(
    raw_trades: pd.DataFrame,
    filter_src1: Optional[str] = None, # pandas.query(filter_src1)
) -> pd.DataFrame:
    return raw_trades.pipe(_filter_data)

This is what I would expect to see between them.