Voting starts in March for the Drupal Association Board election.
This is a sub-issue of.
- Break up migration_dependencies into migration_dependencies:required and migration_dependencies:optional. More config schema friendly, more user friendly. Win all over.
- Provide a schema per load, source and destination plugin. Having source schema per plugin allows to mark certain constants as translatable labels.
migrate.destination.*needs to only contain
plugin: type: string
migrate.destination.entity:filewill need a little more.
- Make process a type: property and document that if you have a translatable thing then don't put it in the YAML rather write a custom plugin and use t(). This will be insanely rare as constants are in the source configuration anyways which, as the previous point states, will have its own schema.