You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Hi, it was not clear to me that the User model property named
UserMetadata
is mapped todata
for Supabase usage. One example that created my confusion is when I would call GetUserById() method where that property is returned and it is nameduserMetadata
. I was able to identify the correct mapping for Supabase usage by inspecting the SignUpWithEmail() where the objectmetadata
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 isdata
and the other isredirectTo
. The current signup methods only includedata
.The text was updated successfully, but these errors were encountered: