Added tests for parameters for complex filters, fixed nested complex filter returning 'possible filtering' when it should have been known

This commit is contained in:
Yair Morgenstern
2023-11-19 00:06:34 +02:00
parent 92d181d282
commit fb1e57668e
3 changed files with 27 additions and 4 deletions

View File

@ -13,17 +13,17 @@ Note that all of these are case-sensitive!
All filters except for `cityFilter` and `populationFilter` accept multiple values in the format: `{A} {B} {C}` etc, meaning "the object must match ALL of these filters"
Example: `[{Military} {Water}] units`, `[{Wounded} {Armor}] units`, etc.
> Example: `[{Military} {Water}] units`, `[{Wounded} {Armor}] units`, etc.
No space or other text is allowed between the `[` and the first `{`.
All filters accept `non-[filter]` as a possible value
Example: `[non-[Wounded]] units`
> Example: `[non-[Wounded]] units`
These can be combined by having the values be negative filters
Example: `[{non-[Wounded]} {Armor}] units`
> Example: `[{non-[Wounded]} {Armor}] units`
These CANNOT be combined in the other way - e.g. `[non-[{Wounded} {Armor}]] units` is NOT valid and will fail to register any units.