mirror of
https://github.com/supabase/supabase.git
synced 2026-09-22 13:37:53 +08:00
24be387cdb
## What kind of change does this PR introduce? Docs update. Aligns documentation and style guides with the **Sign in / Sign out / Sign up** platform standard. Closes DOCS-1328. Related to [#49874](https://github.com/supabase/supabase/pull/49874). ## What is the current behavior? Docs style guides prefer _login_ / _log in_. Guide prose uses mixed login and sign in wording. ## What is the new behavior? - [WORD_LIST.md](apps/docs/WORD_LIST.md) and [copywriting.mdx](apps/design-system/content/docs/copywriting.mdx) document the sign in standard - Design-system auth examples updated - Guide prose and API reference spec descriptions updated ### Terminology **Standard:** Use _sign in_, _sign out_, and _sign up_ as verbs. Use _sign-in_, _sign-out_, and _sign-up_ as nouns and adjectives. Match Studio UI labels (**Sign in**, **Sign out**, **Sign up**). **Preserved intentionally:** | Category | Keep as-is | Example | | -------- | ---------- | ------- | | Feature name | social login | `/social-login`, `features.mdx` heading, OAuth provider section | | URL slugs | `login` in paths | `/phone-login`, `/login-flows`, `choosing-login-flow` | | CLI | `supabase login` / `supabase logout` | Reference ids `supabase-login` / `supabase-logout`; executable commands unchanged | | SDK methods | `logout()` | Kotlin/Swift method names in API reference titles and examples | | Third-party UI | Provider product labels | Facebook Login, Kakao Login, portal **Login** buttons | | Postgres | Database terminology | login privileges, login credentials, login via role | | Audit/logging | Log prose | "Generates the following **log** in the Postgres Logs" | | Code and routes | Paths and filenames | `app/login/`, `Login.tsx`, `demos/android-login` | | External URLs | Third-party login pages | `dash.cloudflare.com/login`, `console.neon.tech/login`, `vercel.com/login` | | API identifiers | Event and field names | Audit actions `login`/`logout`, `should_logout_user` | ## To test - Run `pnpm lint:mdx` in `apps/docs` - Spot-check `features.mdx`, `social-login.mdx`, and a provider guide (e.g. Facebook, Kakao) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Standardized authentication terminology across guides, reference material, CLI documentation, and copywriting guidance using “sign in,” “sign out,” and “sign up.” * Updated authentication instructions, headings, link text, examples, and SSO guidance for clearer, more consistent wording. * Corrected related grammar, spelling, hyphenation, and documentation links while preserving established product names and implementation commands. * **Style** * Refined code examples with consistent import ordering and spacing. * **Examples** * Updated authentication button and menu labels to “Sign in” and “Sign out.” <!-- end of auto-generated comment: release notes by coderabbit.ai -->
190 lines
5.9 KiB
Plaintext
190 lines
5.9 KiB
Plaintext
---
|
|
title: 'Build a User Management App with Angular'
|
|
description: 'Learn how to use Supabase in your Angular App.'
|
|
---
|
|
|
|
<$Partial path="quickstart_intro.mdx" />
|
|
|
|

|
|
|
|
<Admonition type="note">
|
|
|
|
If you get stuck while working through this guide, you can find the [full example on GitHub](https://github.com/supabase/supabase/tree/master/examples/user-management/angular-user-management).
|
|
|
|
</Admonition>
|
|
|
|
<$Partial path="project_setup.mdx" variables={{ "framework": "ionicangular", "tab": "mobiles" }} />
|
|
|
|
## Building the app
|
|
|
|
Start with building the Angular app from scratch.
|
|
|
|
### Initialize an Angular app
|
|
|
|
Use the [Angular CLI](https://angular.io/cli) to initialize an app called `supabase-angular` setting some defaults that you can change to suit your needs:
|
|
|
|
```bash
|
|
npx ng new supabase-angular --routing false --style css --standalone false --ssr false
|
|
cd supabase-angular
|
|
```
|
|
|
|
Install [supabase-js](https://github.com/supabase/supabase-js):
|
|
|
|
```bash
|
|
npm install @supabase/supabase-js
|
|
```
|
|
|
|
Create a `src/environments` directory and save API URL and key that you copied [earlier](#get-api-details) as environment variables in a new `src/environments/environment.ts` file.
|
|
|
|
The application exposes these variables in the browser, and that's fine as Supabase enables [Row Level Security](/docs/guides/database/postgres/row-level-security) by default on all tables.
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/environments/environment.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/environments/environment.ts"
|
|
/>
|
|
|
|
With the API credentials in place, create a `SupabaseService` with `ng g s supabase` and add the following code to initialize the Supabase client and implement functions to communicate with the Supabase API.
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/supabase.service.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/supabase.service.ts"
|
|
/>
|
|
|
|
Optionally, update `src/styles.css` to style the app. You can find the full contents of this file [in the example repository](https://github.com/supabase/supabase/tree/master/examples/user-management/angular-user-management/src/styles.css).
|
|
|
|
### Set up a sign-in component
|
|
|
|
You need an Angular component to manage sign-ins and sign-ups. The component uses [Magic Links](/docs/guides/auth/auth-email-passwordless#with-magic-link), so users can sign in with their email without using passwords.
|
|
|
|
<Admonition type="note" title="Did you know?">
|
|
|
|
You can customize other emails sent out to new users, including the email's looks, content, and query parameters from [the **Authentication > Email**](/dashboard/project/_/auth/templates) section of the Dashboard.
|
|
|
|
</Admonition>
|
|
|
|
Create an `AuthComponent` with the `ng g c auth` Angular CLI command and add the following code.
|
|
|
|
<$CodeTabs>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/auth/auth.component.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/auth/auth.component.ts"
|
|
/>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/auth/auth.component.html"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/auth/auth.component.html"
|
|
/>
|
|
|
|
</$CodeTabs>
|
|
|
|
### Account page
|
|
|
|
Users also need a way to edit their profile details and manage their accounts after signing in. Create an `AccountComponent` with the `ng g c account` Angular CLI command and add the following code.
|
|
|
|
<$CodeTabs>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/account/account.component.ts"
|
|
lines={[[1, 16], [27, -1]]}
|
|
meta="name=src/app/account/account.component.ts"
|
|
/>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/account/account.component.html"
|
|
lines={[[1, 1], [3, -1]]}
|
|
meta="name=src/app/account/account.component.html"
|
|
/>
|
|
|
|
</$CodeTabs>
|
|
|
|
## Profile photos
|
|
|
|
Add a way for users to upload a profile photo. Supabase configures every project with [Storage](/docs/guides/storage) for managing large files like photos and videos.
|
|
|
|
### Create an upload widget
|
|
|
|
Create an `AvatarComponent` with the `ng g c avatar` Angular CLI command and add the following code.
|
|
|
|
<$CodeTabs>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/avatar/avatar.component.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/avatar/avatar.component.ts"
|
|
/>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/avatar/avatar.component.html"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/avatar/avatar.component.html"
|
|
/>
|
|
|
|
</$CodeTabs>
|
|
|
|
### Update the Account component
|
|
|
|
With the Avatar component created, update `AccountComponent` to include it:
|
|
|
|
<$CodeTabs>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/account/account.component.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/account/account.component.ts"
|
|
/>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/account/account.component.html"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/account/account.component.html"
|
|
/>
|
|
|
|
</$CodeTabs>
|
|
|
|
You also need to change `app.module.ts` to include the `ReactiveFormsModule` from the `@angular/forms` package.
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/app.module.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/app.module.ts"
|
|
/>
|
|
|
|
### Launch!
|
|
|
|
With all the components in place, change the contents of `AppComponent` to include the new components and Auth logic:
|
|
|
|
<$Partial path="auth_methods.mdx" />
|
|
|
|
<$CodeTabs>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/app.component.ts"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/app.component.ts"
|
|
/>
|
|
|
|
<$CodeSample
|
|
path="/user-management/angular-user-management/src/app/app.component.html"
|
|
lines={[[1, -1]]}
|
|
meta="name=src/app/app.component.html"
|
|
/>
|
|
|
|
</$CodeTabs>
|
|
|
|
Now run the application in a terminal:
|
|
|
|
```bash
|
|
npm run start
|
|
```
|
|
|
|
Open the browser to [localhost:4200](http://localhost:4200) and you should see the completed app.
|
|
|
|

|
|
|
|
At this stage you have a fully functional application!
|