Bobbie Soedirgo comments

Results 233 comments of


                                            Bobbie Soedirgo

Idea: parse `select` queries to give better types

This looks rad - would be great if this could be made to work with type generation: https://github.com/supabase/postgres-meta/issues/103. I think the hairy part of implementing this is on the less...

Idea: parse `select` queries to give better types

Nice! A grammar would def make this a lot easier.

Idea: parse `select` queries to give better types

Implemented in https://github.com/supabase/postgrest-js/pull/279.

[Feature request] Improve syntax for using typescript "from" function

This is resolved in https://github.com/supabase/postgrest-js/pull/279. It's still a prerelease right now, but will be released as v2 in a few weeks.

Apply "single()" to foreign keys that only one match can be achieved. Automatically or Manually as option.

@madeleineostoja we'll upgrade the PostgREST version on the Supabase platform [soon](https://supabase.com/blog/postgrest-v10) - no need to update postgrest-js or supabase-js.

added option to supply a custom from and to json converter function

Any reason this couldn't just be: ```ts import { parseISO } from 'date-fns'; /// ... client('my_table') .select('*') .match({id: '1234'}) .then(res => { ...res, data: transformData(data) }) /// ... ``` ?

added option to supply a custom from and to json converter function

If you really have to, you can always do: ```js const transformData = data => data.map(row => JSON.parse(JSON.stringify(row), fromJSON)) ``` I can see the value of using `reviver`/`replacer` (e.g. performance...

`error` is returned as `[]` if `.update()` matched no records

Thanks! This seems to be a bug. ~~Can you provide the supabase-js version you used?~~ Nvm, was able to reproduce this on the latest version.

`error` is returned as `[]` if `.update()` matched no records

Same issue when `.range()` is not satisfiable: #324.

Cloudflare workers issues with cross-fetch (xmlhttprequest is not defined)

This should be resolved now afaik. Custom fetch is not needed - the lib now uses the global fetch if available, and otherwise falls back to cross-fetch (previously it always...