AssertionError: "Number" must be defined in MODULE_NAME.field_type_categories.yml when adding any field

Problem/Motivation

With this module enabled, adding any field to any entity type fails with:

AssertionError: "Number" must be defined in MODULE_NAME.field_type_categories.yml in assert() (line 183 of core/lib/Drupal/Core/Field/FieldTypePluginManager.php)

The field type plugins in this module still declare their category as a translatable string, for example category = @Translation("Number"). Since Drupal 10.2 the category key must be the ID of a category defined in core.field_type_categories.yml or in a MODULE_NAME.field_type_categories.yml file. See the change record New API for defining field type categories.

Note that the assertion only fires when assertions are enabled, so this shows as a fatal error on development environments. With assertions disabled the field types are silently dropped into the General group instead of Number.

Steps to reproduce

1. Install a current Drupal 11 site with assertions enabled.
2. Enable Field Expression 2.0.3.
3. Go to any content type and try to add a field.
4. The page fails with the error above. Disabling the module makes it go away.

Proposed resolution

Replace the translatable category strings in every field type plugin with the matching core category ID, for example category = "number" instead of category = @Translation("Number"), and category = "general" where the category is General. The core IDs are defined in core.field_type_categories.yml, so no field_expression.field_type_categories.yml is needed.

The category ID form was introduced in Drupal 10.2, so the module's core_version_requirement should be raised to ^10.2 || ^11. On 10.1 and earlier a plain string category is treated as a literal label and would create a separate group.

Remaining tasks

• Audit all field type plugins in the module and fix each category.
• Raise the core version requirement.
• Review and test on Drupal 11 with assertions enabled.

User interface changes

The Expression field types appear under the Number group on the field selection screen instead of triggering an error or falling back to General.

API changes

None.

Data model changes

None.