Mert YEREKAPAN
df8729a82b
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Chore / dead code removal ## What is the current behavior? The `apps/docs/components/Flag/` directory contained legacy feature flag code that was never wired up: - `FlagProvider.tsx` — all ConfigCat logic commented out; only wraps children in an empty context - `FlagContext.ts` — an empty `createContext({})` with no values ever set - `Flag.tsx` — a gate component that reads from the above empty context, so flags always evaluate to falsy - `hooks/useFlag.ts` — references the dead local `FlagContext` instead of `common`'s `FeatureFlagContext` The docs app already uses `FeatureFlagProvider` from the `common` package (configured in `apps/docs/features/app.providers.tsx`), making this entire local implementation obsolete. Closes [GROWTH-611](https://linear.app/supabase/issue/GROWTH-611/clean-up-deadlegacy-flag-code-in-docs-app) ## What is the new behavior? The dead code is removed: - `apps/docs/components/Flag/` directory deleted - `apps/docs/hooks/useFlag.ts` deleted Any code needing feature flags should import `useFlag` directly from `common`. ## Additional context No flag-gated features were affected — the old local implementation was non-functional (context always resolved to `{}`), so removing it has no behavioral impact.
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.
Versioning
All tools have versioned docs, which are kept in separate folders. For example, the CLI has the following folders and files:
cli: the "next" release.cli_spec: contains the DocSpec for the "next" release (see below).cli_versioned_docs: a version of the documentation for every release (including the most current version).cli_versioned_sidebars: a version of the sidebar for every release (including the most current version).
When you release a new version of a tool, you should also release a new version of the docs. You can do this via the command line. For example, if you just released the CLI version 1.0.1:
npm run cli:version 1.0.1
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.