Manuel Rossard
Manuel Rossard
Having the possibility to specify the types / validation method for parameters would be a very nice improvement! I'd still keep it inside the filter definition though, something that could...
> We should not have a strong link between a filter (parameter) and a property. well there needs to be a way to specify this some way or other, or...
> 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:[...
> 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...
...and i'm actually only talking about search filter when you're talking about all filters, which can't help 😅
> 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...
> I think the `queryLanguageParser` name is not appropriate in all cases. A parameter can be found in `path`, `query` are `header` according to OpenAPI Spec the way we parse...
Haven't investigated further yet, but this option makes some OrderFilters disappear in my current project too.
Actually same exact problem here, the ApiResources having this problem have double uppercase letters in their names...
Forgot this PR...does this fix your issue? https://github.com/api-platform/core/pull/5771