During dependency detection, entity export, migration plugin generation etc, it is (unfortunately) necessary to perform each operation differently based on the type of the actual entity, based on the type of the exported field, etc. In 1.x, this is managed directly in ExportPluginBase or in JsonFiles, by hard-coding the exceptional cases:
This is extremely hard to maintain, makes extending the API nearly impossible if anyone wants to export a custom content entity (or something that's not an entity, but should be handled like an entity, like poll votes for example).
Create plugin system for:
* Managing field value export (FieldValueExporter plugins).
* Handle exceptional, entity-specific cases (Exportable plugins).
Yes, will be documented in the last sub-task of [#3459831}
Fixed
2.0
Code
Please also see if it makes sense to do something with #3313995: Support adding additional dependencies → at the same time.
Automatically closed - issue fixed for 2 weeks with no activity.