[2.0.0-beta2] Enum prop type serialization issue

Thanks a lot Brahim. Can you do a MR instead of a patch?

Why would EnumPropType be the only one needing DependencySerializationTrait?

I'm not sure if this also affects other complex prop types, as I only have a few components in my project, and they all use primitive prop types (boolean, string, etc.) and enum prop type.
I will test with other prop types and create a merge request.

I tested all existing prop types and found no serialization errors. This makes sense since, for example, the variant prop type uses enums, so fixing the issue with the enum prop type should also resolve it for the variant.

A merge request has been opened.

the variant prop type uses enums, so fixing the issue with the enum prop type should also resolve it for the variant.

I am not sure about this sentence.

I tested all existing prop types and found no serialization errors.

This is the most important, I will do the review

The trait DependencySerializationTrait solves two seralization issues. (Correct me if I am wrong.) First if the plugin uses services and second if the plugin uses the translateable markup. EnumPropType uses translateable markup so this is propable the reason for the bug because summary method uses translateable markup.

So I would move this PropTypePluginBase.

Brahim, can you move the trait use to PropTypePluginBase?

@christian.wiedemann
You're right, it would be better to handle this in PropTypePluginBase, ensuring a general fix for all prop types.

@pdureau I'll take care of it.

PHPCS is KO

   | ERROR | [x] Use statements should be sorted alphabetically. The first
   |       |     wrong one is
   |       |     Drupal\Component\Plugin\Definition\PluginDefinitionInterface.
   |       |     (SlevomatCodingStandard.Namespaces.AlphabeticallySortedUses.IncorrectlyOrderedUses)

Careful ( I have rebased the branch on git.drupalcode.org, you may need to delete and repull your local)