- Issue created by @johnv
- 🇳🇱Netherlands johnv
This was blocked by 📌 RenderElement and FormElement base plugin classes are deprecated in 10.3 and removed in 12.0 Postponed , which is now resolved.
Attributes are the new normal (as per D10.3).
POSTPONED UNTIL D12 OR LATER, in order to support D10.2 installations
This is core's policy change record: [#3395575] /
→
And some change implementations:
-
https://www.drupal.org/node/3505422 →
-
https://www.drupal.org/node/3229001 →
Add the Attributes, leaving the Annotations, to preserve backwards compatibility, since the change records states:
"The plugin discovery supports that both annotations and attribute classes are defined on a plugin. Using a non-existing attribute class, will not result in an error, so in earlier version of Drupal core or the respective contributed project, it will fall back to the annotation. The annotation can be removed once a sufficiently recent version of the module providing the plugin type is required."
- convert Hooks to #[Hook('help')] --> having no problems by adding #[LegacyHook]
- convert * @Event() to ...
- convert * @FieldFormatter to ...
- convert * @FormElement to ...
- convert * @FieldType to #[FieldType()]
- convert * @FieldWidget to ...
- convert * @ViewsArgument/~Field/~Filter to ...
And to support other contributed modules:
- convert * @FeedsTarget() to ...
- convert * @FieldDiffBuilder() to ...
- convert * @MigrateField() to ...
- convert * @MigrateProcessPlugin() to ...
- convert * @SearchApiProcessor() to ...
- convert * @WebformElement() to ...
n/a
Example: todo
n/a
Active
1.0
Code
This was blocked by 📌 RenderElement and FormElement base plugin classes are deprecated in 10.3 and removed in 12.0 Postponed , which is now resolved.