Move to plugins

I've basically done with moving hardcoded fields exporting/importing processes to plugins.

Remaining tasks:

• Update README.
• Add field import/export events to allow other modules reacting on import/export and alter fields values (old hooks are now deprecated since they were misused for adding custom field types support).
• Update hooks API documentation, document their deprecation.
• Testing; I verified automated tests and tested a few things manually but I'm not 100% sure everything is in place.

Oh and also exporting base fields (\Drupal\single_content_sync\ContentExporter::exportBaseValues) should be moved to plugins as well; but I guess this should be a followup issue.

There are some new bug fixings and improvements in 1.3.x.

Rebase against 1.3.x is a must

Hi @abramm,

Based on drupal 9 experience, I think we can deprecate hooks in future minor release e.g. 1.5.x. In this case, any deprecated functionality will be completely removed from 2.0.x, so we will not need to release one more major version after 2.x that does not contain hooks.

If you agree I will create one more issue and new minor tag 1.5.x, (1.4.x is still on my agenda to release soon)

Hey @nginex,
You're the boss :).
There's still some work to be done in this MR first though.

Hey @nginex, mind having another look?
The MR is currently based off 1.3.x and is feature complete (including the README).

Hi @abramm, thank you for this hard work, I will review it by the end of the week, If needed I will make some adjustments and move it to the new minor version. I will keep you posted

1. Fix conflicts
2. Apply latest changes from 1.4.x (if any)
3. Fix open issues from the MR
4. Functional testing will be done once the above things are fixed.

Hi @nginex,

That wasn't easy as I had to rebuild the whole branch again :).

All the issues are now resolved; I've also reviewed upstream changes to fields import/export code and updated corresponding plugins accordingly.

I'm a big fan of keeping clean Git history so I did rebase and added all edits to corresponding commits. I believe the right way to merge this is to not use squash as commits history could be important for anyone doing further work.

Please let me know if there's something else needed before this could be merged.

It's finally happening.

Big thanks to @abramm and @Igor Mashevskyi

I'm going to create 1.4.0-beta1 release and create a few issues to handle these todos before we create a final stable 1.4.0 release:

- Update README.
- Add field import/export events to allow other modules reacting on import/export and alter fields values (old hooks are now deprecated since they were misused for adding custom field types support).
- Update hooks API documentation, document their deprecation (how to migrate guide in the documentation).

For now all future fixes and changes in 1.3.x should be also migrated to 1.4.x before we create first stable 1.4.0 release

Created beta1 release. See https://www.drupal.org/project/single_content_sync/releases/1.4.0-beta1 →
Updated homepage of the module. See https://www.drupal.org/project/single_content_sync →

Automatically closed - issue fixed for 2 weeks with no activity.