mirror of
https://github.com/supabase/supabase.git
synced 2026-10-07 10:25:06 +03:00
Szymon MentelandClaude Sonnet 5
21189d2f23
- Link the libpq pipeline-mode doc from the opening sentence.
- Show `{ prepare: false }` in the runnable code samples (troubleshooting
page's fix and the postgres.js quickstart's client setup), not just in
prose, per CodeRabbit review.
- Tighten the pipelining spelling-dictionary entry so it requires a real
suffix instead of matching bare "pipelin". CodeRabbit's own suggested
pattern, [Pp]ipeline(s|d|ing)?, would have broken matching for
"pipelining" (pipeline + ing concatenates to "pipelineing", not
"pipelining"), so kept the existing, correct alternation and only
dropped the trailing `?` that made it too permissive.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KpmtZWQTia6nfJfrYoh4gn
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the developers' guide and contributing guide.