* ci(docs): fix sync process
GraphQL codegen needs to be run before sync because otherwise the types
are missing. Missed this in local testing because codegen had already
been run for other reasons.
* fix(troubleshooting sync): unresolved import
* ci(docs lint): fix commenting workflow
* [bot] sync troubleshooting guides to db
---------
Co-authored-by: Charis Lam <26616127+charislam@users.noreply.github.com>
Co-authored-by: github-docs-sync-bot <github-docs-sync-bot@supabase.com>
* ci(docs): fix sync process
GraphQL codegen needs to be run before sync because otherwise the types
are missing. Missed this in local testing because codegen had already
been run for other reasons.
* fix(troubleshooting sync): unresolved import
* ci(docs lint): fix commenting workflow
Add a script for syncing error codes from the repo to the database. This
is part of the newly created rootSync script, where all sync scripts
should be moved eventually.
* Bump nextjs in the ui-library.
* Bump the nextjs in design-system.
* Bump nextjs to v15 in www.
* Bump the next version in the pnpm catalog.
* Switch all apps to using the catalog version of next.
* Fix ui-lib and design-system to build with next 15.
* Fix some prettier errors.
* Bump the next-eslint package.
* Fix a lint issue about a component starting with underscore.
* Use the catalog version of next in cms app.
* Disable turbo for dev command in www. Remove obsolete experimental flags.
* Return some of the experimental flags.
strictNullChecks was off for docs, which lets errors slip through and
leads to incorrect required/optional typing on Zod-inferred types. This
PR enables strictNullChecks and fixes all the existing violations.
* Added new blog post and modified some docs for SEO
* ci: Autofix updates from GitHub workflow
* Fixed some linter errors
* Update apps/docs/content/guides/database/connecting-to-postgres.mdx
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Update apps/docs/content/guides/database/connecting-to-postgres.mdx
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Show that its setting is persisted in the filesystem at `supabase/.temp/project_ref`, so developers have a way of seeing what project is currently linked.
This appears to be otherwise undocumented, and only mentioned in one Github issue and one Reddit comment as far as I can tell.
* Move all components in ui-patterns into src folder. Add exports field for all files.
* Fix all apps to use the new ui-patterns.
* Fix the design-system build.
* Remove all unused rexports from ui-patterns index. Apps should use direct imports instead.
* Change the tailwind content property to include src folder of ui-patterns.
* Remove autoprefixer from the tailwind configs.
* Remove autoprefixer as a dependency.
* Fix the CVA conditions in FormLayout.
Our environment variables are a bit of a mess, so cleaning them up:
- We have duplicate environment variables that resolve to the same thing
but just have different names, deduplicating all of these
- We have a .env.development (for publicly safe variables) and a
.env.example, we
really only need one
- Privately, we have a .env (for running scripts) and a .env.local (for
Next.js). Changing the dotenv source for scripts, so again we only need
one
Scripts currently use CJS, which is causing a bit of a mess when trying
to use shared utilities from the app. Converting everything to ESM so
there are fewer conflicts when adding new scripts going forward.
* feat(content api): add error endpoint
Add an endpoint to return the details of a Supabase error, given the
error code and service.
Schema additions:
```graphql
type RootQueryType {
"...previous root queries"
"""Get the details of an error code returned from a Supabase service"""
error(code: String!, service: Service!): Error
}
"""An error returned by a Supabase service"""
type Error {
"""
The unique code identifying the error. The code is stable, and can be used for string matching during error handling.
"""
code: String!
"""The Supabase service that returns this error."""
service: Service!
"""The HTTP status code returned with this error."""
httpStatusCode: Int
"""
A human-readable message describing the error. The message is not stable, and should not be used for string matching during error handling. Use the code instead.
"""
message: String
}
enum Service {
AUTH
REALTIME
STORAGE
}
```
* test(content api): add tests for top-level query `error`
Right now we're filtering out third-party extensions by looking for
stack traces that don't touch 'app:///_next'. However, third-party stack
traces do include the Sentry code that sends the error, and that
originates in 'app:///_next'. We need to filter out any events that do
not have 'app:///_next' events beyond that one Sentry frame.
* add replication section with instructions for services
* address comments and neturalise tone
* formalised overview and simplified faq
* reviewdog silenced (mostly)
* move individual tools into tab group and reduce mention of subscriptions
* fix tab components
* correct postgres typos and others
* removed individual service pages and added section for monitoring slots
* update nav menu and add information for monitoring
* update monitoring docs
* added example queries for tracking replication and removed overview
* added spelling rules for Xmin and cleaned up CDC format
* edits & reorganization
---------
Co-authored-by: Charis Lam <26616127+charislam@users.noreply.github.com>
* refactor(docs): turn auth error codes table into data file
Take the Markdown error codes table and turn it into a data file
instead. This makes it easy to parse and reuse in other places besides
Markdown documents.
* Update apps/docs/content/errorCodes/authErrorCodes.toml
Co-authored-by: Terry Sutton <saltcod@gmail.com>
---------
Co-authored-by: Terry Sutton <saltcod@gmail.com>
Alter the docs test script so it spins up Supabase locally. Will allow
for end-to-end tests against the local DB.
Also small alteration to one of the test files to silence an annoying
(but intended) error.
The "required properties" that need to be disabled are actually listed
in the code block, but it's not entirely clear from the way that it's
written that it's the case, leading to user confusion. Added a line to
make that explicit.
Fixes DOCS-233
Should've double-checked this before applying the filter =_=""" but
apparently filtering out `app:///` also filters out legitimate events,
since those files are prefixed by `app:///` as well.
Instead let's keep only `app:///_next` since that should include all our
static JS assets.
* 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>
Charis