supabase / supabase-flutter / 27618738259 / 3
85%
main: 85%

DEFAULT BRANCH: main
Ran
Files 5
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 93.013%. Remained the same
27618738259.3

push

github

web-flow 
feat(examples): add passkeys example with shared local Supabase setup and launcher (#1407)

## What kind of change does this PR introduce?

Adds an `examples/` directory with a runnable example showing off the
passkey (WebAuthn) support, plus shared local Supabase infrastructure
and a launcher so the same setup can be reused by future examples.

> Based on #1408 (passkey ceremony helpers). Review/merge that first;
this PR targets its branch and GitHub will retarget it to `main` once
#1408 merges.

## What is the new behavior?

### `examples/passkeys`
A Flutter web app demonstrating passkeys with `supabase_flutter`:

- Create an account / sign in with email and password
- Register a passkey for the signed-in user
- Sign in with an existing passkey (no password)
- List, rename and delete passkeys

The full WebAuthn ceremony (including the platform prompt) is handled by
`supabase_flutter` via `registerPasskey()` and `signInWithPasskey()`
from #1408, so the example just calls those. The web build loads the
`passkeys` plugin's JavaScript bundle in `web/index.html`. The README
explains, concisely, what is needed to use passkeys.

### `examples/supabase`
A single shared `config.toml` every example runs against. It enables
passkeys (`[auth.passkey]` + `[auth.webauthn]`), disables email
confirmations for quick sign in, and trims the stack to the data plane
(turns off Studio, the email-testing server, Edge Functions, and
analytics) so `supabase start` is lean.

### `examples/launcher`
A small Dart TUI (`examples/run.sh`) that boots the local Supabase
stack, reads back the local URL and publishable key, lists the examples
and runs the selected one on Chrome with the credentials wired in as
`--dart-define`s. It stops the stack on exit if it started it. New
examples (any directory with a `pubspec.yaml` and `lib/main.dart`) are
discovered automatically.

A root `examples/README.md` explains the whole workflow.

## How was it tested?

- `flutter analyze` / `dart ana... (continued)

426 of 458 relevant lines covered (93.01%)

2.11 hits per line

Source Files on job storage_client - 27618738259.3