[Rest] NumericFilter and RangeFilter on the same property triggers an error

[jdeniau]

API Platform version(s) affected: 2.*

Description

Creating both NumericFilter and RangeFilter on the same key triggers the following notice :

At least one value is required, multiple values should be in "schemaVersion[]=firstvalue&schemaVersion[]=secondvalue" format

This issue is similar to #3483 but for REST and the error is not as blocking.

Possible Solution

I would go for the same possible solution as @epourail : implementing [eq] and [neq] for the range filter, this way, the NumericFilter could be only used for "simple" search, and the RangeFilter superseed the NumericFilter for complex searches.

I can open a PR on that if you want to, and it may fix #3483 too.

[soyuka]

We'd end up having a complex numeric filter. There was a discussion about filters somewhere (can't find it), having some kind of RFC for filters would be nice, but also complex to maintain. IMO for advanced use case developers should create their own.

found it: api-platform/api-platform#639
#2400
#2055

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.