...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.
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
...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
orcollective.jsonmigrator.remotesource
blueprints, so it can be confusing to work out why a pipeline isn't being seen (for example one usingcollective.jsonmigrator.jsonsource
).There are three possible action points as I see it, we can use more than 1 of them.
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@@mr.migrator
view in these docs@@jsonmigrator
view from this productAny thoughts? @thet or anyone else?