Filter with nested source does not work correctly

[wmwart]

duplicate the issue #5361 as how it got closed but is now actual again

I expected that when adding a filter field to the screen (without entering any value), nothing happens to the current list. Instead, a request is sent to
getList posts {"pagination":{"page":1,"perPage":10},"sort":{"field":"published_at","order":"DESC"},"filter":{"comment":{}}}
and the list becomes empty.

This differs from the behavior of adding a filter for a non-nested field — until a filter value is entered, no pre-request is sent.
The difference in behavior for the user is not obvious.

Often the fields of nested filters are named as if it were a field of the current resource and it is difficult to explain to the user why it works differently.

here's a link Codesandbox https://codesandbox.io/s/aged-https-f8ynv?file=/src/posts/PostList.js with last packages versions

1. Add a filter comment.title to the Posts list view.
2. Get unwanted filtering

no, you indicated that you fixed that in 3.9.6 https://github.com/marmelab/react-admin/releases/tag/v3.9.6

I was confused that when I updated the application a couple of weeks ago to 3.9.6 everything worked for me. I was delighted and removed some of the crutches in my backend. Everything worked in the release build. However, when yesterday they began to reassemble the release, the filters again stopped working correctly...
They searched for a long time and determined that if you slip a yarn.lock two weeks ago, then everything works.
Hence the conclusion - something has changed in your dependencies.

• React-admin version: 3.10.4
• Last version that did not exhibit the issue (if applicable): 3.9.6

[fzaninotto]

Reproduced and confirmed, thanks.