Would you consider implementing a feature which iteratively creates filtered decks for each subtag?
Since filtered decks cannot be nested, it would create empty decks which contain the filtered deck.
For example, creating a filtered deck from the parent Block1 tag would create several empty decks for the parent tags, and filtered decks for the childless tags.
I think this should be a separate option. If it were the only option, then cards which only have the tag of the parent (e.g. tag:Block1::Week1 but not tag:Block1::Week1::*) would be missed.
I do not think automatically building of these iteratively-generated filtered decks is necessary, since it can be an expensive operation with more complex tagging.
Would you consider implementing a feature which iteratively creates filtered decks for each subtag?
Since filtered decks cannot be nested, it would create empty decks which contain the filtered deck.
For example, creating a filtered deck from the parent
Block1tag would create several empty decks for the parent tags, and filtered decks for the childless tags.I think this should be a separate option. If it were the only option, then cards which only have the tag of the parent (e.g.
tag:Block1::Week1but nottag:Block1::Week1::*) would be missed.I do not think automatically building of these iteratively-generated filtered decks is necessary, since it can be an expensive operation with more complex tagging.
Thank you for the awesome add-on!