yes I will add the resti n this pr as well

for the other document what do we do

if it is a string we pass to url ?
if it is a tensor we pass to tensor field ?

@anna-charlotte what do u think ?

yes I will add the resti n this pr as well

for the other document what do we do

if it is a string we pass to url ? if it is a tensor we pass to tensor field ?

@anna-charlotte what do u think ?

So instead of identifying one main content field per predefined doc we decide based on the input data's type? Could also make sense, but lead to confusion if multiple fields have the same type. E.g. some Document might have two fields of type str, then we need to choose one of those

So instead of identifying one main content field per predefined doc we decide based on the input data's type? Could also make sense, but lead to confusion if multiple fields have the same type. E.g. some Document might have two fields of type str, then we need to choose one of those

but we do this only for the one that make sense. But nothing automatic

Yes, I like it, too, especially with `Text(text='some text') its too verbose, with the others I don't mind too much.

Could also make sense, but lead to confusion if multiple fields have the same type

Yes not sure about this, too, could be a bit confusing maybe if for most we pass str to url, but for Text we pass it to the text field. But still, I think i like passing the obvious ones, like tensor to tensor field etc, instead of only on main content field

But nothing automatic

What do u mean by this?

but glad we aren't trying to do everything at the same time for once
we don't this at the BaseDocument level but tat at predefined document level. We don't come up with a generic solution but rather we decide for each Document

For the Audio doc we could do the same, right? @samsja

For the Audio doc we could do the same, right? @samsja

I forgot this one

📝 Docs are deployed on https://ft-feat-validate-docs--jina-docs.netlify.app 🎉

partially fix : #1056