Wildcard exclusion support via "~"

Created on 1 March 2019, over 5 years ago
Updated 9 September 2024, 2 months ago

Problem/Motivation

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.test

The 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.

Proposed resolution

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...

Remaining tasks

Patch, review.

User interface changes

Wildcard exclusion support via "~" in the "Additional configuration" box. Potentially description text under the box. Example.

API changes

None.

Data model changes

None.

✨ Feature request
Status

Needs work

Version

2.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States chrisolof

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Needs documentation

    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.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡±Netherlands seanB Netherlands

    Thanks, #6 worked for us when the line with ~ is placed first:

      - '~homebox.homebox.test'
      - 'homebox.homebox.*'
    

    Adding tags for tests and documentation.

  • πŸ‡ΊπŸ‡Έ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.

  • πŸ‡ΊπŸ‡ΈUnited States chrisolof

    The attached patch against 2.0.x:

    - adds a sort into the mix so that entry order of inclusions and exclusions is no longer important
    - adds documentation of how to exclude under the textareas where exclusions can be entered
    - updates some code comments to make it clear that we're working with exclusions as well as wildcards

    Tests are still needed here.

Production build 0.71.5 2024