It seems (I am not an expert by any means) that beyond the 3 strategies described here, you can also connect to Supabase using the clients -- but that doesn't get mentioned here. For those just learning Supabase, like me, I feel like this would make the documentation clearer.
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
* Passthrough the sentry env vars to studio so that the sourcemaps are uploaded correctly.
* Fix the Turbo command in the Dockerfile.
* More fixes to the Dockerfile.
* Set the primary key as the default sort if no other sort exists
* Rename
* Add contextual toast messages when trying to update/delete row on table with no PKs
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
Adapts the tax id view to the new MGMT-API endpoints. Users can now only manage a single tax id instead of adding multiple.
Besides
- Use non-deprecated fetchers
- Use Shadcn components
Fix missing typo in the api introduction document
Changes text from `Authorization Bearer <supabase_personal_token` to `Authorization Bearer <supabase_personal_token>`
* Don't create a new image whenever a new tag is published on supabase/supabase.
* No need for an input when triggering a new build.
* Enable the latest tag for all pushes.
* Bump the version of turbo to 2.0.3.
* Fix the breaking changes in turbo config.
* Make the npm version more loose.
* Fix the build command for the database-design app.
* Try adding some env vars to the turbo for www.
* Add more missing env vars.
* Bump the turbo version to 2.0.4.
* Remove SUPABASE_SERVICE_ROLE_KEY from docs#build since it's used by other scripts, not by build.
* Add all apps to the turbo config. Sort the configs by name.
* Add eslint-config-turbo to all apps.
* Add environment vars to all apps in the turbo configs. These were reported by the eslint-turbo config.
* Move the eslint preset into a separate package.
* Import the next package into all apps. Remove redundant packages.
* Import the new eslint rules.
* Update the package-lock.
One of our bigger papercuts in terms of billing is customers not understand compute pricing and that they cannot launch unlimited projects for $25 in total per month. Customers also get confused with "Compute Hours" on their bill.
We already show a breakdown of compute hours/compute costs on the organization billing and usage pages. While that can be improved in the future, this PR aims to make compute costs much more clear when launching a new project.
This should avoid "surprise" compute charges and serves as kaizen improvement. Info is only shown for paid plan organizations, as it's irrelevant for free plan organization.
* Refactor login_page with a _showSnackBar function
* Add an onError block to onAuthStateChange
Errors get swallowed without this error handler, I noticed it when I had requested too many magic link emails, there was no feedback in the ui, nor in the logs in the console.
* Fix SnackBars not being displayed and add a _showSnackBar function
* Fix code samples for login_page.dart and account_page.dart to reflect fixes in #27104
* Fix isError not being passed for an Unexpected Error in login_page
* Update flutter user management example to a more modern code
* Update the guide to match the new content
* run formatter
* got rid of excess code and minor format fix
---------
Co-authored-by: dshukertjr <dshukertjr@gmail.com>
Terry Sutton