alex
fb0f2f7b9b
- Remove inline edit modal from projects listing page - Add Settings link to project cards navigating to /projects/:id/settings - Reposition Open Workspace button to rightmost action for easier access - Update tests for new UI flow - Update documentation to reflect new editing workflow - Sync specs: frontend-foundation and project-management Quality gates: npm run lint passed
37 lines
1.4 KiB
Markdown
37 lines
1.4 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Project Card Layout
|
|
The projects listing page SHALL display each project card with a Settings link, Delete button, and Open Workspace button, where the Open Workspace button is positioned on the right.
|
|
|
|
#### Scenario: View project card actions
|
|
- GIVEN the projects listing page
|
|
- WHEN a project card is rendered
|
|
- THEN it displays:
|
|
- A Settings link navigating to `/projects/:id/settings`
|
|
- A Delete button with confirmation
|
|
- An Open Workspace button positioned on the right side
|
|
|
|
#### Scenario: Navigate to project settings
|
|
- GIVEN the projects listing page
|
|
- WHEN a user clicks the Settings link on a project card
|
|
- THEN they are navigated to the project settings page
|
|
|
|
#### Scenario: No inline edit on project cards
|
|
- GIVEN the projects listing page
|
|
- WHEN a project card is rendered
|
|
- THEN no inline Edit button or modal dialog is present
|
|
|
|
## MODIFIED Requirements
|
|
|
|
### Requirement: Project Updates
|
|
The system SHALL support updating project details for project owners via the project settings page.
|
|
|
|
#### Scenario: Update project via settings
|
|
- GIVEN a project owner viewing the project settings page
|
|
- WHEN they update the name or description and save
|
|
- THEN the changes are persisted
|
|
|
|
#### Scenario: Non-owner update denied
|
|
- GIVEN a user who is not the project owner
|
|
- WHEN they attempt to update project details via the settings page
|
|
- THEN the system responds with forbidden status |