default-content-export-references behaves differently than default-content-export

Remaining tasks

Find consensus, patch, commit

I see three of ways to bring the two commands into alignment. I personally like the way `dce` prints to the console, so I wrote a patch that does the same for `dcer` instead of printing to the current location.

Perhaps the more sensible option, which keeps behavior in line with current behavior, is to make all the arguments required.

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment almost 2 years ago →
🇺🇸United States kevinfunk
I have a need to only export nodes and not references. I added this feature while working on this issue. Please let me know if you think it doesn't belong as part of this issue.

Export all nodes (does not export references)
drush dce node --folder=modules/custom/my_custom_module/content

Export only node 1
drush dce node 1 --folder=modules/custom/my_custom_module/content
Comment almost 2 years ago →
🇺🇸United States kevinfunk
Comment almost 2 years ago →
System Message
The last submitted patch, 11: default_content-2824103-11.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.
Comment almost 2 years ago →
🇺🇸United States kevinfunk

default-content-export-references behaves differently than default-content-export

Problem/Motivation

Proposed resolution

Remaining tasks

Comments & Activities