- 🇺🇸United States dasginganinja Bethlehem, PA
Is this feature still on the books? 🤔
- 🇨🇭Switzerland bircher 🇨🇿
it could be....
We would just have to sort the list like config ignore does so that it doesn't matter what order you put the strings in.
It would be nice to be able to provide a wildcard but then exclude a few individual items from the split. Example:
webform.webform.*
~webform.webform.testThe example above would add all webforms to the split except for the one with id: test. Support for this exists currently in the Config ignore module, and the "~" character is used to achieve it.
Add wildcard exclusion support via the ~ character.
Here's how config_ignore does it (for reference):
https://cgit.drupalcode.org/config_ignore/tree/src/Plugin/ConfigFilter/I...
Patch, review.
Wildcard exclusion support via "~" in the "Additional configuration" box. Potentially description text under the box. Example.
None.
None.
Needs work
2.0
User interface
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
A documentation change is requested elsewhere. For Drupal core (and possibly other projects), once the change has been committed, this status should be recorded in a change record node.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is this feature still on the books? 🤔
it could be....
We would just have to sort the list like config ignore does so that it doesn't matter what order you put the strings in.