Consistent handling of "unexpected" filtering

[katamartin]

It's currently possible to deselect all category values by using an arbitrary category filter ('none', 'foo', etc.). This allows us to show a nice "filtered out" empty state when deselecting all categories on the frontend.

using filter like: http://offsets-db.fly.dev/projects/?category=none

However, the same is not supported for registry (See https://offsets-db.fly.dev/projects/?registry=none). Is it possible to consistently either (a) support unexpected filter values by simply not returning results if nothing matches or (b) support specific a filter value that can be used for deselection like none ?

[andersy005]

@katamartin, this should be fixed

❯ http 'https://offsets-db.fly.dev/projects/?registry=none'                                                                                                               ─╯
HTTP/1.1 200 OK
content-encoding: gzip
content-type: application/json
date: Tue, 31 Oct 2023 14:38:12 GMT
fly-request-id: 01HE32QCR66XBEKANBQZR939BF-lax
server: Fly/7328d5b5 (2023-10-27)
transfer-encoding: chunked
via: 1.1 fly.io

{
    "data": [],
    "pagination": {
        "current_page": 1,
        "next_page": null,
        "total_entries": 0,
        "total_pages": 0
    }
}