search

computerminds / cm_config_tools

DEPRECATED: Mirror of http://cgit.drupalcode.org/cm_config_tools
1 stars 0 forks source link

Report better on exporting #7

Open anotherjames opened 8 years ago

anotherjames commented 8 years ago

Currently, the command either says it has successfully operated, or not. It should:

1) Say what was was exported - or, better, what will be exported, similarly to the import command's preview, before asking for confirmation? 2) If no modules were found to export to, say so, rather than just being mysterious, since that's a common edge case where developers just need to add the cm_config_tools key to a module's info file.

anotherjames commented 8 years ago

Now at least reports saying that no config was found to export when there were no changes written.

darthsteven commented 7 years ago

We should differentiate or make clearer that 'There is no config to export. ' means that it's worked, found the config that it should export, but doesn't need to etc. I thought that maybe it hadn't found any config to export at all.

darthsteven commented 7 years ago

Maybe we should also output keys that are explicitly 'managed' (maybe also implicit and unmanaged) but don't correspond to actual config in the site. This would help with adding a new item, as I'd see immediately that I'd got the name wrong or somesuch.