Andrew Valleteau

> The error wasn't in my MRE example from before but in our main codebase, but going back and booting up the MRE again revealed that the problem wasn't your...

It seems that this bug has already been fixed in the latest version of the Supabase CLI. I wanted to take a look at this, so I tried to reproduce...

Coverage complain for no reason there. Edit: Exclude `types.ts` from coverage, there isn't really anything to cover there.

I think the answer has been given in the first comment, type checking cannot infer the result types from a runtime value. So the "type" of the string you provide...

Thanks for reporting this, @CalvinWilkinson! Is there errors from auth/db container logs? That might help us reproduce the issue. Also, are you using the latest CLI version as @saltcod mentioned?...

> PS: Is there a way to split the `seed.sql` across multiple files, actually I'm creating `fixtures` into `migrations` folder to achieve it. Hey ! We just merged https://github.com/supabase/cli/pull/2702 that...

Hey @vijaemanlapaz In order to help you it would be helpful to know: 1. Did you upgraded `supabase-js` recently ? From which version to which version ? 2. This seems...

Hey there, I'm currently working on this issue in PR supabase/postgrest-js#554. I've added more tests to ensure better consistency between runtime behavior and type inference results. Hopefully, this will cover...

Hey everyone ! We've reworked the result inference in `postgrest-js` to address the typing issues mentioned above. The changes are available in a canary release, and we're actively seeking your...

The fix has been released in `supabase-js` v2.46.0. I'm closing this issue, but feel free to reopen or open a new issue if you encounter any further errors.