mirror of
https://github.com/supabase/supabase.git
synced 2026-09-06 18:11:51 +08:00
ca2b50a0a7
Follow-up to #48344: collapses the two resolution paths for the Admonition module into one. `src/admonition.tsx` was a back-compat shim re-exporting `src/Admonition/`. Two ways to resolve one module is exactly what produced the macOS self-import bug fixed in #48344, and the local typecheck errors that #48374 worked around. This removes the shim and standardizes on the PascalCase subpath, matching every other export in the package. **Changed:** - Codemodded all 246 `ui-patterns/admonition` imports to `ui-patterns/Admonition` (240 `.tsx`, 5 `.mdx`, 1 `.ts` across studio, docs, www, design-system, and lite-studio) - Pointed the 5 internal `'../admonition'` imports back at the `'../Admonition'` directory **Removed:** - `packages/ui-patterns/src/admonition.tsx`, and its `./admonition` entry in the exports map (regenerated with `pnpm gen:exports`) ## To test - `grep -r "ui-patterns/admonition" --include='*.ts*'` → no hits - `pnpm test:case-hazards` → passes - `pnpm typecheck` → all 15 tasks green - `pnpm --filter studio run lint:ratchet` → passes - `pnpm --filter ui-patterns vitest run src/Admonition` → 11 tests pass <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Standardized Admonition component imports across the application and documentation. * Improved compatibility with case-sensitive environments by using the canonical component path. * Removed the legacy Admonition import entry point. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alaister Young <10985857+alaister@users.noreply.github.com>
41 lines
1.6 KiB
Plaintext
41 lines
1.6 KiB
Plaintext
import { Admonition } from 'ui-patterns/Admonition'
|
|
|
|
## Prerequisites
|
|
|
|
Before you begin, ensure you have the following:
|
|
|
|
- **A Textlocal account**: Sign up for [TextLocal](https://www.textlocal.com/signup) to start sending SMS messages.
|
|
- **A Supabase project**: Necessary for SMS authentication integration. Create your project in the [Supabase Dashboard](https://supabase.com/dashboard).
|
|
- **A mobile phone**: To receive SMS messages and test your setup.
|
|
|
|
## Setting up Textlocal as your SMS provider
|
|
|
|
To integrate Textlocal with Supabase:
|
|
|
|
1. [Get a Textlocal API key](#get-a-textlocal-api-key)
|
|
2. [Customize your sender name](#customize-your-sender-name-optional)
|
|
3. [Configure your Supabase project](#configure-supabase)
|
|
|
|
### Get a Textlocal API key
|
|
|
|
1. Log into your Textlocal account and go to `Settings` > `API Keys`.
|
|
2. Generate a new API Key. Save your new API key in a safe location.
|
|
|
|
### Customize your sender name (Optional)
|
|
|
|
Textlocal defaults to `TXTLCL` as the sender name for all messages. You can customize this to better reflect your brand:
|
|
|
|
1. In your Textlocal dashboard, go to `Settings` > `All Settings` > `Sender Names`.
|
|
2. Change your sender name.
|
|
|
|
### Configure Supabase
|
|
|
|
To set up Textlocal as your SMS provider in Supabase, follow these steps:
|
|
|
|
1. In your Supabase Dashboard, go to the [Auth Providers section](https://supabase.com/dashboard/project/_/auth/providers).
|
|
2. From the list of available authentication providers, select `Phone`.
|
|
3. Toggle `Enable Phone Provider`.
|
|
4. Under `SMS Provider`, select `Textlocal.`
|
|
5. Enter your Textlocal API Key and Sender Name.
|
|
6. Customize your SMS Message (optional).
|