40 lines
1.1 KiB
Markdown
40 lines
1.1 KiB
Markdown
# Task: Frontend Invite Acceptance
|
|
|
|
## Goal
|
|
|
|
Build the invite acceptance route and connect it to registration or sign-in.
|
|
|
|
## Feature Spec
|
|
|
|
- `docs/FEATURES/workspace-invites.md`
|
|
|
|
## Scope
|
|
|
|
- Add a public route for invite acceptance links.
|
|
- Load display-safe invite details from the token.
|
|
- If the user is signed in with the invited email, allow direct acceptance.
|
|
- If the user is signed in with a different email, show a clear mismatch state.
|
|
- If the user is signed out, route them to sign in or register and resume acceptance afterward.
|
|
- Refresh the current user profile after acceptance so the new workspace appears.
|
|
|
|
## Constraints
|
|
|
|
- Frontend runtime config must flow through `frontend/src/config.js`.
|
|
- Feature-owned code belongs under `frontend/src/features/workspaces`.
|
|
- Do not add a marketing-style landing page for invite acceptance.
|
|
|
|
## Likely Files
|
|
|
|
- `frontend/src/router/router.js`
|
|
- `frontend/src/features/workspaces/`
|
|
- `frontend/src/features/workspaces/stores/workspaceStore.js`
|
|
- `frontend/src/locales/en.json`
|
|
- `frontend/src/locales/fr.json`
|
|
|
|
## Validation
|
|
|
|
```bash
|
|
cd frontend
|
|
npm run build
|
|
```
|