feat: support negative globs

[pd93]

Fixes #225

This PR adds native support for negating a glob pattern in Task. e.g.

version: '3'

tasks:
  css:
    sources:
      - 'mysources/**/*.css'
      - '!mysources/ignoreme.css'
    generates:
      - 'public/bundle.css'

It works by looping over an array of patterns in order. If a pattern is normal, the files are added to a map with a value of true (i.e. the files should be included). if a pattern begins with a !, then all the files matched by that pattern are added to (or updated in) the map with a value of false (i.e. they should not be included). We then loop through the map and convert all keys with a value of true into a slice. This slice is then sorted and returned.

[krystian-panek-wttech]

I just tested it. thank you @pd93

It works like a charm <3 however the '!' needs special care as it is special character in YML. without it it is possible to encounter:

https://stackoverflow.com/a/22235064

my working example:

  aem:build:
    desc: build AEM application using Maven
    sources:
      - pom.xml
      - all/pom.xml
      - all/src/**/*
      - core/pom.xml
      - core/src/**/*
      - ui.apps/pom.xml
      - ui.apps/src/**/*
      - '!ui.apps/src/main/content/jcr_root/apps/mysite/clientlibs/clientlib-{site,dependencies}/**/*'
      - ui.apps.structure/pom.xml
      - ui.apps.structure/src/**/*
      - ui.config/pom.xml
      - ui.config/src/**/*
      - ui.content/pom.xml
      - ui.content/src/**/*
      - ui.frontend/pom.xml
      - ui.frontend/*.js
      - ui.frontend/*.json
      - '!ui.frontend/package-lock.json'
      - ui.frontend/src/**/*

I hope it will be released soon ;)

[andreynering]

To avoid YAML issues with ! we could move to a proper key like not:, ignore: or exclude:. What do you think?

version: '3'

tasks:
  css:
    sources:
      - mysources/**/*.css
      - exclude: mysources/ignoreme.css
    generates:
      - public/bundle.css

I think I would chose exclude:, but I'm open to opinions.

[krystian-panek-wttech]

yep, it's nice ;) also opting for exclude

[krystian-panek-wttech]

can't wait to see it released ;) @andreynering

[leaanthony]

Yeah, exclude: is great 👍

[andreynering]

Hey @pd93,

Can you change to use exclude:? Once done, we're ready to merge this.

[krystian-panek-wttech]

@pd93 any chance that you will do it this month? :) From my perspective it's pretty annoying and I would be glad to have it improved. If you have no time to complete this, just let me know I will improve it.