Enum priority change in symfony-dev

[soyuka]

symfony/symfony@c87e4a1 makes our sf-dev test fail it needs investigation

[GwendolenLynch]

features/graphql/mutation.feature fails as this now returns a string

core/src/GraphQl/State/Processor/NormalizeProcessor.php

Line 88 in 53a45d7

$data = $this->normalizer->normalize($itemOrCollection, ItemNormalizer::FORMAT, $normalizationContext);

… and throws an exception a little bit lower

core/src/GraphQl/State/Processor/NormalizeProcessor.php

Lines 105 to 107 in 53a45d7

	if (null !== $data && !\is_array($data)) {
	throw new \UnexpectedValueException('Expected serialized data to be a nullable array.');
	}

The origin is where api_platform.graphql.normalizer.item sets the serializer.normalizer tag priority

core/src/Symfony/Bundle/Resources/config/graphql.xml

Lines 225 to 226 in 53a45d7

	<!-- Run after serializer.denormalizer.array but before serializer.normalizer.object -->
	<tag name="serializer.normalizer" priority="-995" />

For reference, the BackedEnumNormalizer has changed its priority from -915 to -880. I couldn't find an easy single substitution that didn't break other tests, so shall leave this to the experts.

[soyuka]

nice thanks for debugging this, I guess that we need to update our priorities from the Symfony docs it's not a bc-break to change a service priority :/ (although it does break code).