Closed taw closed 3 years ago
foreign:
operator is sort of a side thing, but it works now.
I'm not really sure what want to do with any: queries. They work OK, but I don't think I want to switch to these as default like I originally considered. So I'll close it for now, might revisit in the future.
So I added any: operator which can search for whatever you want:
any:"Jaya Ballard" any:sorcery
- one is artifact mentioning "sorcery" in Oracle textany:"Wayne England" any:mythic
any:Gideon any:creature
any:"Décomposition abrupte"
any:green any:dragon
- also includes some fairly loose resultsThe idea is that it could actually become the default search term so
blue "win the game" enchantment
is translated intoany:blue any:"win the game" any:enchantment
, which is basicallyc>=b o:"win the game" t:enchantment
by current system. Any explicit operators would still work, and there are some finer points to consider.Todo list:
2/4 ISD Spider
going too far?), trying a few questionable things is the only way to know for sureany:Gideon
matchedt:Gideon
andft:Gideon
cards, and it feels like the type or name is much stronger match.any:red
matchesft:hired
, which is counterintuitiveforeign:
operator for any foreign name matchesOf course it could turn out that the whole idea is misguided.