Merge pull request #81 from trails-cool/archive-completed-changes
This commit is contained in:
commit
05b5f6febf
13 changed files with 49 additions and 0 deletions
|
|
@ -50,3 +50,25 @@ The Planner SHALL display an elevation profile chart for the current route.
|
|||
#### Scenario: Show elevation profile
|
||||
- **WHEN** a route is computed
|
||||
- **THEN** an elevation profile chart is displayed below the map showing distance vs elevation with total ascent/descent statistics
|
||||
|
||||
### Requirement: Planner home page
|
||||
The Planner home page SHALL provide a clear call-to-action to create a new planning session and a link back to the home page from within sessions.
|
||||
|
||||
#### Scenario: Home page CTA
|
||||
- **WHEN** a user visits the Planner home page
|
||||
- **THEN** a prominent "Start Planning" button is visible that links to `/new`
|
||||
|
||||
#### Scenario: Session home link
|
||||
- **WHEN** a user is in a planning session
|
||||
- **THEN** the header contains a link back to the Planner home page
|
||||
|
||||
### Requirement: Map cursor rendering
|
||||
Other participants' cursors on the map SHALL be clearly visible with proper styling.
|
||||
|
||||
#### Scenario: Cursor appearance
|
||||
- **WHEN** another participant moves their mouse on the map
|
||||
- **THEN** a colored pointer icon with their name tag appears at the cursor position
|
||||
|
||||
#### Scenario: Cursor does not obscure map controls
|
||||
- **WHEN** cursors are rendered
|
||||
- **THEN** they appear below map controls (zoom, layer switcher) in z-index
|
||||
|
|
|
|||
|
|
@ -94,3 +94,30 @@ The Planner SHALL NOT collect, store, or track any personal user data. Sessions
|
|||
#### Scenario: Anonymous session participation
|
||||
- **WHEN** a user joins a session without any account
|
||||
- **THEN** the user is assigned a random color and temporary display name with no data persisted about their identity
|
||||
|
||||
### Requirement: Session participant awareness
|
||||
Users in a planning session SHALL see who else is present and be able to identify themselves.
|
||||
|
||||
#### Scenario: Participant list visible
|
||||
- **WHEN** multiple users are in a session
|
||||
- **THEN** the header shows each participant's name and color
|
||||
|
||||
#### Scenario: Host badge
|
||||
- **WHEN** a participant is the routing host
|
||||
- **THEN** their entry in the participant list shows a host indicator
|
||||
|
||||
#### Scenario: Edit own name
|
||||
- **WHEN** a user clicks their own name in the participant list
|
||||
- **THEN** an inline text input appears to change their display name
|
||||
|
||||
#### Scenario: Name persisted
|
||||
- **WHEN** a user changes their name
|
||||
- **THEN** the name is saved to localStorage and immediately visible to all other participants via awareness
|
||||
|
||||
#### Scenario: Join notification
|
||||
- **WHEN** a new participant joins the session
|
||||
- **THEN** a brief toast shows "[name] joined"
|
||||
|
||||
#### Scenario: Leave notification
|
||||
- **WHEN** a participant leaves the session
|
||||
- **THEN** a brief toast shows "[name] left"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue