How to avoid triggering dot notation in filters input source and use it as string

Hi,

I would like to use nested properties filters https://api-platform.com/docs/core/filters/#filtering-on-nested-properties but in order to do so I need to provide querystring like this endpoint?city.name=search which I cannot do because react-admin filter will generate endpoint?city[name]=search out of next example due to dot notation thing.

<Filter {...props}>
    <TextInput label='City' source='city.name' alwaysOn />
</Filter>

It looks like it goes into redux-form and jsx feature set, but how do I escape dot in this case?

Cheers.

[diimpp]

@modiodio Hi

I’ve extended vendor SearchFilter into my own src/Filter/SearchFileter and overloaded apply method with replacement of __ with ., therefore all subsequent php-side dot notion logic was untouched and working as before.

[mauchede]

Hi @diimpp,

Thank you for the report. I did not use yet a nested filter, so I can not give any solutions now. But we currently work a lot on the filter system. I will check this soon and I will update this issue when I will have a solution.