Joel Lee

Wow this is old and I confess I don't recall the context around this - @mansueli just looping you in case relevant to the implementation of the lib

Hey team, Thanks for patiently waiting. Can I check if this is still an issue?

Hey team, An update on this thread - could y'all try updating the Supabase version [like in this PR](https://github.com/supabase/auth-ui/pull/255) and see you can listen on the event? There was a...

@ozanmakes Thanks for trying it out, we'll get back to you shortly

Hey @mosnicholas, Yes, It is possible to create a user and set `app_metadata` as you wish when creating a user. ``` const { data, error } = await supabase.auth.admin.createUser({ email:...

Hey @mosnicholas, Thanks for the comprehensive overview - I may be missing something but I agree that we should probably set the `params.AppMetadata` together with the provider fields before creating...

Hey @mosnicholas, Sorry, I missed the past messages. I've forgotten a large part of the context but you might be able to use [custom claims auth hooks](https://supabase.com/docs/guides/auth/auth-hooks) to achieve your...

Short update here - we're doing a quick scan for update triggers to see how we can move ahead

Notes for Testing 1. After this change an update trigger on auth.user should continue to receive the same app_metadata 2. After this change any app_metadata passed in via createUser should...

More notes: I'm not sure that 1. will continue to hold. It looks like if we do the update prior to creation: ``` if params.AppMetaData != nil { if terr...