Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapped property UserMetadata for User model #16

Closed
fplaras opened this issue Dec 25, 2021 · 2 comments
Closed

Mapped property UserMetadata for User model #16

fplaras opened this issue Dec 25, 2021 · 2 comments

Comments

@fplaras
Copy link

fplaras commented Dec 25, 2021

Hi, it was not clear to me that the User model property named UserMetadata is mapped to data for Supabase usage. One example that created my confusion is when I would call GetUserById() method where that property is returned and it is named userMetadata. I was able to identify the correct mapping for Supabase usage by inspecting the SignUpWithEmail() where the object metadata is assigned to "data" exactly how it is labeled on the js library. The usage of these values under the authentication templates would be {{ .Data.FullName }} for anyone looking to use them this worked for me. I also noticed that there are 2 properties for options one is data and the other is redirectTo. The current signup methods only include data.

@acupofjose
Copy link
Collaborator

@fplaras thanks for all the feedback! I'll address these shortly. A Merry Christmas to you friend!

@acupofjose
Copy link
Collaborator

The signature now has a specific class for it, SignUpOptions that has both of these options available with clarified comments.

Available in supabase-csharp@0.2.11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants