If I want the user to validate their identity in the app with security questions to reset their password, I think that should be my design choice, right? Forcing SMS and email auth seems like guiderails...

Ability to update password using the API

I think Supabase needs playgrounds for the client libraries. I find myself much preferring to write views in datagrip, because I can do that in easily with instant feedback, then check the results and make sure I'm getting what I want. Writing a JS query requires me to run the app and check the console log or the component data. TLDR: I want to test JS SDK queries against my database like I can test SQL queries

cc @User

Client playgrounds

Hey supabase team, no big suggestions, but the font size of the code snippets in the docs is very small.

its very hard for me to read stuff without zooming into

thanks.

Documentation accessibility

the feedback's isn't working

Please make modals not disappear without confirmation. been typing up a policy here only to have it disappear when I misclicked the Review button

the font size of code in policy editor is very very very small

Add Supabase 'App' modules to Integromat for all REST operations.

Allow csv imports even after table has been created

Perhaps a way to share sql code in the editor so teams can share certain function’s sources?

add a button in the table view that generates sql to create that table

Yeah, same when you are creating a new table and press Escape, it dismisses the whole thing 😕

Thoughts on adding a "Login" button to the supabase.io website? I keep getting confused if I really want to "start your project" when I'd like to "continue your project" 🙈

Integromat

Just discovered this export all rows to csv button hidden under the ID column dropdown. Perhaps it should be under a More options button on the toolbar instead?

this was a function I wanted but didn't realise existed! +1 on moving it somewhere more obvious

makes sense - noted

Would be great to have

provider

field from

auth.users

, that way we'll know what OAuth provider they used to create an account

you can get provider with

raw_app_meta_data->>'provider'

Ooooo. Thanks!

Could we put multi-region deployments on the radar? https://fly.io/docs/getting-started/multi-region-databases/ Fly.io is a great way to deploy an app, it would be good for performance if we could deploy our supabase instance on Fly along with the app..

Another suggestion, I was having a hard time debugging RPC/Trigger Function Would be great to have a UI into the Supabase Dashboard for all the error logs. It's hard to figure out which part of the code was breaking and it's only returnign status

500

We originally wanted to ship FunctionHooks with logs - this is worth looking at again i think. for RPC/Triggers, we could perhaps have an example on how to log them, or we actually have logs for functions/triggers created via supabase dashboard since we already automate some of their creation anyway.

Yes an example would be great! 🙂

Hey everyone, request from our team: shared sql scripts across the team. We're running a lot of reports from Supabase. It's pretty silly to write a script, then manually share it with someone else so they can run it when it's already on the platform. We don't need any permissions, etc. Just a shared script section (tbh it's fine if all are shared for us, but understand not everyone would want that)