At the moment withIncludeAncestorsRemove is defined to only add !deep filters for all known parents. However, if you use ** you can't know all parents beforehand. So for those glob paths, besides the known parents, we should add the actual, full glob path (for NODE_REMOVED only that is) to the condition (using the trick to not add deleteSubtree which otherwise filters out subtree deletion).
As a result you get different events based on the glob path:
- for all known parents you get an event if one of those parents get removed
- if you have a glob path registered, then you get an event for all matching paths should a parent of those nodes get deleted