* Adding note to broadcast_changes that is uses a private channel.
2 customers confused so far on need for RLS and private flag set to use this function.
* Update apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
* Added <$CodeTabs> to Pages Router tab
There was an inconsistency between the App Router and Pages Router page, which was only a small detail.
* Update apps/docs/content/guides/auth/server-side/nextjs.mdx
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
When translation tools go over prices, they wrongfully convert USD into other currencies without changing the price. $25 becomes Rp25 (Rupiah).
By using `translate='no'` we avoid the translation of pricing info. There are some tooltips left that are not covered yet, but this should be the majority already.
Kept the docs Pricing component as simple as possible, just wrapping in a span to avoid translation, not modifying any formatting.
Correct the code examples for the Clerk third-party auth docs:
- Fix TypeScript error
- Change RLS policy check to accept both [Clerk v1 and v2
JWTs](https://clerk.com/docs/backend-requests/resources/session-tokens)
Pulled code samples from an example app that I've checked in to make
maintenance and testing easier in the future.
The alert "Make sure your local database is stopped before diffing your schema." appears after completing the diff step.
It would be more useful to display it before performing the diff, to ensure that "supabase stop" is executed beforehand and not afterward.
- The docs explain "If you want the data returned as `text`, use the `->>` operator."
- Only the SQL example shows this using the `description` field
- All language should use `->>` for the description field
* Update all docs that make references to the database settings to find the connection strings.
Update all docs that references the database settings for the compute and disk page
* run prettier
* run pnpm format instead of prettier directly.
* first run through, fix grammar and reword awkward sentences
* Fix typos and remove unnecessary whitespace
* Apply suggestions from code review
Co-authored-by: Tyler <dshukertjr@gmail.com>
---------
Co-authored-by: Tyler <dshukertjr@gmail.com>
Before:
Instructions for restoring a backup locally were buried inside the
Upgrading guide.
After:
Instructions for restoring a backup locally are on their own page in the
Local Development section. This page is linked from the Upgrading guide
because it is useful if a paused project has exceeded its restoring time
limit.
Han Qiao