Any way to control input or output types such that I can use ABCs such as Mapping? I'd like to not collapse my ChainMap into a dict, but right now the Builder can't link up one node that returns a Mapping (on top of ChainMap) into another node that requests a Mapping. I realize the automatic discovery may be intractable or ambiguous. Any ideas in this direction?

Do you have a code example to reproduce this? That would help me understand.

Not working:

cfg: collections.abc.Mapping[str, str] = [...]
result = driver.execute(
     inputs={
        "study_config": cfg,

[...]
def config(study_config: dict[str, str]) -> Config:
    [...]

Fix: (collapse Mapping into dict]

"study_config": dict(cfg),

@Mattias Fornander US so it does something smarter than that, but it’s not perfect. New type-checking cases that we haven’t evaluated. You can override it with this hook https://hamilton.dagworks.io/en/latest/reference/lifecycle-hooks/EdgeConnectionHook/

@Mattias Fornander US we just need to modify check_input_type (since it appears to be an issue with validating the object against the type, and not with constructing the graph) and therefore add to the test case here. Actually @Mattias Fornander US I think that is expected behavior, no? Mapping is a superset of dict. Every

dict

is a

Mapping

, but not every

Mapping

is a

dict

. My suggestion here would be to change the annotation on

study_config

...