Steve Axtmann

No problem. Thank you for the explanation and potential short-term solutions! I believe that the best short/long-term solution for us will be to split up these queries so we have...

> Not my MR but any reason #194 didn't end up getting merged? @kav It was my MR & it was still missing things like tests and I hadn't gotten...

> Need a hand taking it the rest of the way? I too would love LIKE and ILIKE support Yeah that's absolutely cool with me! [My changes](https://github.com/Flambe/pg_graphql) have been the...

My original plan was to go the PostGraphile way since it's similar to the existing options like `neq`, but the PostgREST style is definitely closer to how it works on...

No problem! I didn't realise that views would have these extra complications so I can definitely understand why they aren't supported yet. Thank you for the detailed response!

If anyone is looking to use like/ilike filtering with the new rust version of the library, I've updated my fork to include them and some basic steps on how to...

If there is still a consideration for an opt-in version then that'd be perfect! (startswith wouldn't be enough to cover our usecase) I would have attempted it myself already but...

I'd love parity with Supabase JS, but yeah I fully understand the concerns you've mentioned before. Splitting it into opt-in/opt-out parts sounds really useful for me at least!

The static code analysis fails on the second half of the echo which I haven't touched, so I do not believe that this is related to my PR? `$(fn_human_readable_file_size ${filesizetotal}...

we had the same issue (but running it via docker, not netlify) and the fix was to prefix the env with `NUXT_PUBLIC_` e.g. `NUXT_PUBLIC_SUPABASE_URL` (except the service key which is...