Not surprised the collection creator was not able to help with this, as that is unfortunately not possible with the existing filter system. The issue is that because “markup” is a string, you can only perform string operations on it. Substrings within the markup that happen to be numbers are still just strings. This is why for the markup you can only check for equality / contains / within.
Adding such a filter would require parsing the content of all your cards and checking to see if there are numbers, and if there numbers then allow the user to perform number operations on them, which is all just a bit too messy.
However, depending on what type of range we’re talking about, what you can do is have a somewhat exhaustive series of contains
filters to check your entire range, one number at a time.
If you wanted cards with a specific tag and a number somewhere between 3-7, it would look like this.
{
"type": "group",
"op": "and",
"filters": [
{
"type": "tag",
"op": "contains",
"arg": "numeric"
},
{
"type": "group",
"op": "or",
"filters": [
{
"type": "markup",
"op": "contains",
"arg": "3"
},
{
"type": "markup",
"op": "contains",
"arg": "4"
},
{
"type": "markup",
"op": "contains",
"arg": "5"
},
{
"type": "markup",
"op": "contains",
"arg": "6"
},
{
"type": "markup",
"op": "contains",
"arg": "7"
}
]
}
]
}
While this obviously can work for a small range of numbers, I certainly wouldn’t do this for a range like 1-100 as I think the performance would suffer in all sorts of ways.
What range were you wanting to find?