Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow "3/2 mikasa" to be a valid search term #60

Open
seiyria opened this issue Dec 6, 2022 · 2 comments
Open

allow "3/2 mikasa" to be a valid search term #60

seiyria opened this issue Dec 6, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@seiyria
Copy link
Member

seiyria commented Dec 6, 2022

this might require tagging everything as x/y and adding tags to the default search? how does bare search handle these cases?

@seiyria seiyria added the enhancement New feature or request label Dec 6, 2022
@ronelm2000
Copy link

imho, x/y should just be a shorthand for: level:x cost:y -c:climax since that's what's usually expected, tho, I'm more surprised there's no or operator (like | or or typically used in compound search)

there's definitely room for plugging 1/1 or 2/2 set:MTI to search for standby targets.

@seiyria
Copy link
Member Author

seiyria commented Feb 9, 2023

It definitely should be! That seems like a fair shorthand to me.

Right now, or does exist in some limited capacity, for example: c:g,r would search for green or red cards (the syntax page seems to mark it as and which is not correct, not sure what I was typing). But it wouldn't allow cross-or searching like 1/1 or 2/2 - maybe something like 1/1,2/2 set:MTI could work for this operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants