Incorrect types in variables used in Drupal\Core\Field\Annotation\FieldType

Can be the test fails as i left @ingroup plugin_translatable but the var now is set as \Drupal\Core\Annotation\Translation|array? or it is not related and failed another thing?

Test passed (failed due to an unrelated issue)

Left a comment but MR appears to still be in draft.

Sorry, i forgot to remove the draft the last time.
Replied to the comment with one example where an array is used in core :)

Believe my 1 question has been addressed.

Added some questions on the MR.

Implemented suggestions

Feedback appears to be addressed.

I'm triaging RTBC issues → . I read the IS, the comments and the MR. I didn't find any unanswered questions or other work to do.

Leaving at RTBC.

Where in the code is description set to an array? I don't think this part of the change is correct. Category is now a string. And we should link to \Drupal\Core\Field\FieldTypeCategoryManager here now because this string should be a field type category plugin.

Oh I see... in things like \Drupal\Core\Field\Plugin\Field\FieldType\TimestampItem - now that's an odd change. But hey ho.

So I think we should still improve this to say that when you provide an array it'll be used to create a bulleted list - if it is not an array then it'll be just displayed as a sentence.

And we should link the category to \Drupal\Core\Field\FieldTypeCategoryManager and say it should match a field type category plugin ID

Is it possible for someone to add a new CR to ✨ Make field selection less overwhelming by introducing groups Fixed about the support for an array of translatable strings in the field type plugin definition and what it does.