Consider splitting the IriConverter in 2 classes

[lyrixx]

I got the following error with Symfony

Circular reference detected for service "api_platform.hydra.normalizer.entrypoint", path: 
api_platform.hydra.normalizer.entrypoint
-> api_platform.iri_converter
-> api_platform.item_data_provider
-> app.api.data_provider.agent_rule
-> app.elasticsearch.straight_rule
-> serializer
-> api_platform.hydra.normalizer.entrypoint".

Basically, my "agent_rule" are stored in Elasticsearch. So I have a custom DataProvider. This one depends on the serializer (because We serialize/unserialize data to/from Elasticsearch).

AFAIU, the IriConverter does 2 symmetrical things: Item <-> IRI.
I think i would ease the development if theses 2 things would be in 2 different classes to avoid such circular reference.

WDYT?

[dunglas]

Good idea! 👍 on my side (at least two interfaces).

[soyuka]

👍 two interfaces seems great, this should be easy to implement