You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
In some case an entity can have a property of type array, and we should want to store it in Elasticsearch as nested or object depending the kind of search we want.
But, if we configure the bundle to store the property as type: nested for example we have an error because the Transformer do not handle the case of a non-object.
Do you think, it will be accepted to do a change in the original transformer ?
The main document should be an object, but all fields and subfields should be what we want, I don't know if the best way is:
keep this workarround directly in the Transformer (pro: do not redesign all, cons: this is a little weird)
do a redefine the functions type hints to handle object or array ? (pro: better design, cons: update the transformer design for a edge-case)
The text was updated successfully, but these errors were encountered:
Hi,
In some case an entity can have a property of type array, and we should want to store it in Elasticsearch as nested or object depending the kind of search we want.
But, if we configure the bundle to store the property as
type: nested
for example we have an error because the Transformer do not handle the case of a non-object.Actually I've a workarround:
In the config, I just set:
Do you think, it will be accepted to do a change in the original transformer ?
The main document should be an object, but all fields and subfields should be what we want, I don't know if the best way is:
The text was updated successfully, but these errors were encountered: