Seva Maltsev

@dependabot rebase

@dependabot rebase

That's how the current search behaves: the AND OR and NOT are boolean operations. The rules return `true` when satisfied and `false` otherwise. So you can go as granular as...

How do you envision this query language? With the current setup, I think it can be something like this: ```SQL AND ( perks: [1st: has these 3], lottery(not implemented): [...],...

There can be optimizations of the perk serch to reduce the ORs to a single rule

:thinking: Thanks, this is interesting. I've elected a drag-and-drop approach because it's very intuitive to do, and mobile-friendly. I'm dissatisfied with the search as well, so I have the desire...

I wouldn't say it was the primary focus – I intentionally gather a very limited amount of info on usage, but do know that tablets are not that small of...

Cool! Thanks @denis-rossati I'll go through the issues, add comments, and make it more contribution-friendly. (there is a long-running branch called map-gen-updates that has lots of changes and I'll merge...

I did that initially, but thought it would be in the spirit of the mimic to be a heart in the UI. The description text for it is its name!

Thanks! I agree, this is convenient. I'll add it once I'm updating that part of the codebase