drush-ops
Fixes #3793 Can not create new config via cset
Sorry for 2 year delay!
This makes sense, but on the other hand its handy for most users to validate this. So, I'm thinking we keep validation on but prompt to ask user if we should proceed. That prompting should be done in cset itself, and not the validation (i.e. handle the validation exception).
Thanks for looking into this! Unfortunately i won't be able to work on this any soon.
That prompting should be done in cset itself, and not the validation (i.e. handle the validation exception).
That wont work. Needs more thought.
Could you create a yaml file outside of drush and then do config:import --partial?
(config:import --partial) Thanks! But: That would be no win compared to "edit config-export and cim".
Your plan to use interaction sounded reasonable and i did not get why it's not feasible.
Otoh why not simply create? Typos? We may add a message "Config created - or was it a typo?" so users who created config due to a typo can cdel then. No kittens harmed.
May I add a respectful +1 for @geek-merlin's suggestion just to create the config object please @weitzman?
As far as I can tell, a mis-typed configuration name won't do any harm to the site.
Best wishes,
Alex
