Fix misleading usage examples for config:set and config:delete commands #4085
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I fell into that mistake that naively believed the syntax the usage hint suggested and ran this command like this:
$ drush config:set system.site page.403 filter/tips
When tested the results in browser, I got the regular exception from Drupal core:
Although Drupal's GUI still lacks of consistency on how to properly request users to type in internal URL paths (with or without leading slashes), at least on the CLI side Drush could do better. Let's help future fellows not to fall again into this pitfall I learned today. Once they took the time to check
--help
before running the actual command, that examples should really help them, not misleading.