No, won’t be ok. Some type options can’t be negated, because they are not implicitly enabled by default, consequently negating them must not affect implicitly enabled type options. I have been thinking about that case since a while to simplify filter creation. A more common case:
Turns out that internally I had to support this conceptually (for the
document option), and I have been considering adding a type option which would be a shortcut for the whole set of type options which are implicitly enabled when no types are specified:
Or for your use case:
any would internally be the equivalent of
any is not a good keyword, I can’t figure one that would make it clear it’s an alias for a combination of all discrete network request types.
You can go ahead and open an issue for this, as said I have been considering since a while now, it potentially simplifies filter creation.