Antoine Bluchet

Instead of this we should just consider inputs and outputs as resources so that they take the exact same path as a resource would and therefore you'd get all the...

I don't think this is right, actually look at this: https://github.com/api-platform/core/blob/cbc803cab81bc6acbe74c4db4eba63bc8539aa16/src/Serializer/AbstractItemNormalizer.php#L436-L452 The call at: ``` $propertyMetadata = $this->propertyMetadataFactory->create($context['resource_class'], $attribute, $options); ``` can probably just be something like: ``` $propertyMetadata =...

https://github.com/api-platform/core/blob/main/tests/Fixtures/TestBundle/ApiResource/Issue5648/DummyResource.php#L25-L31 ? Not sure what you're trying to do `force_resource_class` is an internal thing not sure you should use this yourself...

sorry for the delay, thanks for the reproducer

thanks!

It's expected there is a name collision when filter services get declared on your second filter. The best thing for that kind of use cases is to specify filters as...

because we don't support multiple declaration like this for filters, you should use a service to solve the problem, also #5995 will help with that

use a filter service (on the docs open the `yaml` code tab)

not sure how to fix this it's quite hard, to you really need the resolver? can't you use a provider instead?

Haven't merged that yet as I still maintain 3.1 and 3.2 which may need this change before `main`