AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Update query in postgresql9/2/2023 ![]() The upload and update function returns the path of the object uploaded as the path parameter.We now make use of union types which only mark the data as null if there is an error and vice versa. ![]() ![]() Functions types used to indicate that the data returned could be null even if there was no error. Removed signUpWithEmail, signUpWithPhone in favor of signUp.Removed signInWithEmail, signInWithPhone in favor of signInWithPassword.Removed sendMobileOTP, sendMagicLinkEmail in favor of signInWithOtp.Moved resetPasswordForEmail, getUser and updateUser to the GoTrueClient which means they will be accessible from the th namespace in supabase-js instead of having to do to access them.Renamed the api namespace to admin, the admin namespace will only contain methods that should only be used in a trusted server-side environment with the service role key.Indicates that the incorrect credentials were passed.Indicates that a cookie is expected but missing.Indicates that a session is expected but missing.No more throwing of random errors, gotrue-js v2 always returns a custom error type: ( PR).Deprecated and removed setting for multitab support because getSession() and gotrue’s reuse interval setting takes care of session management across multiple tabs ( PR).getSession() will always return a valid session if a user is already logged in, meaning no more random logouts. Deprecated and removed session(), user() in favour of using getSession() instead.signIn method is now split into signInWithPassword, signInWithOtp, signInWithOAuth ( PR).By default, this will be namespace-d with the supabase project ref. supabase-js client allows passing a storageKey param which will allow the user to set the key used in local storage for storing the session.Use undefined instead of null for function params, types, etc.TypeScript typings have been reworked PR.shouldThrowOnError has been removed until all the client libraries support this option ( PR).To set a custom access_token jwt instead, pass the custom header into the createClient() method provided: ( PR) All changes # A refresh token never expires and can only be used once.ĭeprecated and removed setAuth(). The expiry of an access token can be set in the "JWT expiry limit" field in your project's auth settings.We have the following rate limits in place to guard against brute force attacks. Any email links and one-time passwords (OTPs) sent have a default expiry of 24 hours.If you are using auth and you want to set persistSession to true, you will need to provide a custom storage implementation that follows this interface. This warning message can be safely ignored if you're not using auth on the server-side. If you want to set persistSession to true, please provide a storage option or you may set persistSession to false to disable this warning. No storage option exists to persist the session, which may result in unexpected behavior when using auth. When using the supabase client in an environment that doesn't support local storage, you might notice the following warning message being logged: ![]() ![]()
0 Comments
Read More
Leave a Reply. |