Gwendolen Lynch

> I disagree it should be IRIs Easy. I had incorrectly interpreted/assumed parts of what you explained in https://github.com/api-platform/core/pull/6288#issuecomment-2037383301 while trying to mentally reduce it down to the base parts.

> Properties of type \BackedEnum should always normalize to the enum ->value not an iri I presume this is also invalid then?

To be sure I understand correctly, these would roughly be the PHP classes that your example's implementation would have? ```php #[ApiResource] class VideoGame { public GamePlayMode $playMode; } #[ApiResource] enum...

> not sure that we really want to set up rules for plain JSON I couldn't agree more. :+1: Honestly, I am just endlessly getting confused by what an **PHP**...

_**tl;dr:** it looks like the `name` field is what should be used for data "exchange", and the `value` field is reserved for data storage._ > Wouldn't a patch on `webonyx/graphql-php`...

For the alternate option, `GraphQL\Type\Definition\EnumType` can be extended and is created/injected here https://github.com/api-platform/core/blob/5e908c898dd6dca3a6abfd3f083e4d7b4fc4e85a/src/GraphQl/Type/TypeBuilder.php#L216-L217

Symfony have merged [#54484](https://github.com/symfony/symfony/pull/54484) so I've taken this out of draft. I've added a conflict for `6.4.6 || 7.0.6` of `symfony/framework-bundle` and that should have core covered.

> I reverted the priority change on our source code https://github.com/api-platform/core/commit/2a8767108690c35d873a936f9e2383365fdb4f00 Suggestion on that, it is probably safe to revert the change to `docs.feature` as well. Oh, and it is...

> I really like this but I won't be able to merge it right away as we need to work on the Hydra implementation. No stress. I was more trying...

To catch future versions of some of the issues hit, I have added test for `int` and `string` enum resources, as well as GraphQL tests too. ~The latter seems to...