Debugging filters on supabase collections

[NicolasLatitudes]

Hello weweb team ,

I’d like to point out something quite painful when debugging my supabase collections.
When the collection returns no result, the filters appear as somehow empty, at least for the field and operator part.

This has been discussed in a previous post, (see the link at the end of my message), but it’s very hard if not impossible to debug previously written filters, if you have no ways to even SEE what the filters are.

I understand that the filters need at least one non null result to display, but as weweb already knows the fields of all Supabase tables, wouldn’t it be possible to make the fields and operators appear anytime, regardless of the current results.

That would simplify A LOT the usage of weweb.

Thanks a lot for your answer,

Nicolas

Supabase collections : datetimetz fields mistaken as "object"

Hello WeWeb team I experiment a rather painful issue with Supabase Data Collections. My collection has advanced fields, including two dates (date_de_debut / date_de_fin, please don’t judge this awful french naming I claim no responsibility on it ) [image] Yet, when I try to filter my collection, those two fields appear as “object” [image] And because of that I can apply just three kinds of filters on them [image] although I’d like to have filters like “date greater…