Sebastian Husch Lee
Sebastian Husch Lee
@OGuggenbuehl that sounds good!
Perhaps we could rename the field to `haystack.component.type_qualified_name` or `haystack.component.fully_qualified_type`? Otherwise I agree we should be providing the fully qualified type for the component so they are easy/straightforward to inspect...
Alternatively @vblagoje to be more consistent with how we normally provide fully qualified types in our other type fields we could change the `"haystack.component.type"` to have the fully qualified type...
> Yeah both are good but fully_qualified_type is more precise and explicit Okay let's go for that then!
@julian-risch I'm wondering about closing this. This doesn't seem to have come up in practice and perhaps throwing an error makes sense to encourage the user to create their own...