Problem/Motivation

It would be useful to have a dry run option which shows you what would be imported, but doesn't save anything.

Steps to reproduce

Proposed resolution

I can see two ways to do this:

a. Big hammer approach -- replace ALL the entity storage handlers on submit with dummy versions

b. pass a value in the import context, and expect all processors to respect it

We also need a way to collect what's been imported and output the list.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork entity_share-3533226

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

joachim created an issue. See original summary.

dgroene’s picture

dgroene commented

I have an idea about this. Rather than trying to do a dry run on the client that goes through all the processing but simply doesn't save... what if we built an endpoint on the SERVER (which has all the data and doesn't need to make jsonapi requests and serialize/unserialize data) where you could pass your configuration, such as max recursion, and it would use the settings and same relationshipHandleable logic to walk through the content and discover the list of nested entities to be included. The client would get this manifest and may do some further processing (respecting the setting to skip importing entities that haven't changed seems like it would be particularly challenging) to present the list in a preview on the pull form.

dgroene’s picture

dgroene commented
Assigned: Unassigned » dgroene

dgroene opened merge request !169