Problem/Motivation
cckfield plugins were introduced to make migrating cck fields easier but we're now using the same plugin type for D7 fields as well.
This is confusing for developers as 'CCK' was primarily a Drupal 6 concept whereas Drupal 7 had the same functionality in core under the name 'Field'.
Proposed resolution
Rename the plugin type to 'FieldPluginBase' as suggested in #2631736: Cckfield Plugins must distinguish core versions to make it less confusing.
Introduce a backwards compatibility layer for 'CckFieldPluginBase' so that classes that extend that base class don't stop working.
Remaining tasks
The patch in #112 has become too unwieldy to review, so we will split the patch in two:
- The conversion of the CckFieldPuginBase class to just FieldPluginBase, BC layer and required changes to the core migrations using the CCK field plugins. A single conversion a class extending the CckFieldPluginBase.
- All the other conversions of classes extending CckFieldPluginBase and their unit tests. This will be reviewed and handled in a follow-up issue. See follow-up: #2833206: Convert Migrate's cckfield plugins to use the new field plugins in migrate ymls
- The split is now accomplished. The patch was shrunk by 30kb as a result and now has only the *necessary* changes.
- Review of the patch is also accomplished. Now all that is left is to commit the patch.
User interface changes
None.
API changes
No API breaks but two deprecations:
- Deprecated the CckFieldPluginBase class, and add a new FieldPluginBase class.
- Deprecate plugin manager class 'plugin.manager.migrate.cckfield', add 'plugin.manager.migrate.field' service.
Data model changes
None.
