I'll try open a PR to make it dynamic 🙂

@User see this https://github.com/supabase/supabase/pull/4591

I just left a comment

Yeah, its broken cause the supabase team need to allow the vercel deployment 😦

Sorry for the ping but \cc @User

Hey don't ping the team for PRs unless it's an urgent fix. We will looking at github issues and PRs everyday, so we will definitely get to it 🙂

Ah sorry, now I know for future 🙂 Didn't see about when ping was ok in the rules. Sorry again 😦

No worries at all. Really appreciate your contributions💪🏼

Thanks 🚀

Would be extremely useful if supabase implemented transaction / batching functionality akin to firebase's. See: https://firebase.google.com/docs/firestore/manage-data/transactions

Not fun / dev-friendly to have to write an RPC for every atomic operation you want to do 😄

Related discussion and issue: https://github.com/supabase/supabase/discussions/526 and https://github.com/supabase/supabase-js/issues/87#issuecomment-739537955

added to discussion https://github.com/supabase/supabase/discussions/526#discussioncomment-1855387

Is Supabase getting app analytics? If not, that's a suggestion.

Also, the ability to change the required password length might be nice

Please stop having conversations in this channel, create a thread and have your conversations in that. This channel is meant for suggestions and ideas for Supabase. I will be deleting any messages unrelated to Supabase.

Rolling the secret jwt token would be very good

Maybe plans for making aggregations with the select method (like SUM(salary))

Hey folks! the support page is broken and returns 500 error codes.

Please don't @ individuals from the team, members of the team actively watch this channel and take note of what is posted

Support page broken

I suggest adding the ability to query (read-only) the auth.users table directly with a service key. Many production apps need this ability...

js
// In my case, I need to add additional users as 'owners' of a record using their email address

// Find user by email
const { data, error } = await supabase
  .from('auth.users') // Not possible now
  .select()
  .eq('email', 'user@gmail.com')

// Then use the user's data for some business logic

Some developers have used workarounds like creating a public.users table which replicates relevant data from the auth.users table using triggers. This feels like a hacky workaround to me... I would much rather avoid this unnecessary redundancy / potential for data inconsistency down the line. (See: https://nikofischer.com/supabase-how-to-query-users-table) Edit: I've copied this feature request to the git repo: https://github.com/supabase/supabase/issues/4715

I can see how you view that as a workaround but couldn’t you consider it a benefit to separate the actual db auth and functionality from your app’s permissions? Seems like you could easily get into a risky situation without an intentional abstraction.

Using triggers is the best way! Even though it's data duplicated it still is safer as you can use RLS and your not accessing the GoTrue service's data on its own

Querying auth.users with service key

Idea: document what

.setAuth()

doesn't do - I see people trying to use it like it's an API for signing in with access_token, when it seems to be a very low level tool.

.setAuth docs

Enable commands /user-info and /server-info for everyone (suggestion from @User)

It would be nice if there's an api to trigger sending email confirmation, since I've set my smtp server and templates

It would be nice to have a click click click interface to duplicate project or migrate project, so to easily have an updated stable/production project mirroring dev