Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 293830

The recipe script should have a "why-not" equivalent

$
0
0

Problem/Motivation

When working on a recipe, when the script fails to apply (particularly because of existing config that doesn't match) there isn't much useful detail on where the differences are. This can be particularly frustrating when you have just updated the recipe to include configuration just exported from the site itself. It would be great to have an option to have the script cite exactly where it perceives differences.

Proposed resolution

Either add a separate script or a flag for the existing script, so that the person running the script will get useful output on what specific elements have a mismatch with existing configuration. This could be equivalent to running composer why-not [project].


Viewing all articles
Browse latest Browse all 293830

Trending Articles