Antoine Bluchet
Antoine Bluchet
We should not have a strong link between a filter (parameter) and a property.
Because it's locking filters to behave like a parameter is always tight to a property which isn't the case. Something preferable would be: ``` #[ApiFilter(SomeFilter::class, properties:[ 'exposedName' ], filters: [...
This is why I have a `property` but also an array `attributes` in my `Parameter` suggestion so that we can add a link, but the link itself is not at...
Not a problem, in fact I want to cover most of the possibilities and doing a search filter like you have in mind should be possible but there are some...
I think that `itemUriTemplate` helps to solve that kind of use cases especially https://github.com/api-platform/core/pull/5663. In fact we improved the whole system on 3.1, in 2.7 it was always the first...
It's quite hard as we want to be as up to date as possible but it's really hard to support many versions. We definitely need to propose an update to...
indeed I think we should add some backward compatibility
It looks like there are still some issues regarding schemas? I'm waiting for someone to come back with an update as 3.2.14 just came out
just add `object !== null` in your Expression language?