collective / collective.jsonmigrator

JSON based migrations for Plone
GNU General Public License v2.0
8 stars 21 forks source link

Should we retire the jsonmigrator view... #22

Open djowett opened 8 years ago

djowett commented 8 years ago

...in favour of mr.migrator's similar but more powerful @@mr.migrator view?

@@jsonmigrator ignores pipelines that don't contain one of the collective.jsonmigrator.catalogsource or collective.jsonmigrator.remotesource blueprints, so it can be confusing to work out why a pipeline isn't being seen (for example one using collective.jsonmigrator.jsonsource).

There are three possible action points as I see it, we can use more than 1 of them.

  1. Add collective.jsonmigrator.jsonsource to blueprints that @@jsonmigrator looks for - but we would need to also update the view to enable arguments to that blueprint to be edited in the form - something that is already available in @@mr.migrator
  2. Advise using @@mr.migrator view in these docs
  3. Remove @@jsonmigrator view from this product

Any thoughts? @thet or anyone else?

zmijunkie commented 6 years ago

I cannot build mr.migrator at the moment and I am lucky I can use @@jsonmigrator https://github.com/collective/mr.migrator/issues/15