chore(openspec): archive query-tool change and commit remaining updates
This commit is contained in:
egg
@@ -4,7 +4,7 @@
|
||||
TBD - created by archiving change reject-history-query-page. Update Purpose after archive.
|
||||
## Requirements
|
||||
### Requirement: Reject History page SHALL provide filterable historical query controls
|
||||
The page SHALL provide a filter area for date range and major production dimensions to drive all report sections, and SHALL provide context-aware option narrowing for exploratory filtering.
|
||||
The page SHALL provide a filter area for date range and major production dimensions to drive all report sections.
|
||||
|
||||
#### Scenario: Default filter values
|
||||
- **WHEN** the page is first loaded
|
||||
@@ -23,20 +23,11 @@ The page SHALL provide a filter area for date range and major production dimensi
|
||||
- **THEN** it SHALL include reason filter control
|
||||
- **THEN** it SHALL include `WORKCENTER_GROUP` filter control
|
||||
|
||||
#### Scenario: Draft filter options are interdependent
|
||||
- **WHEN** user changes draft values for `WORKCENTER_GROUP`, `package`, `reason`, or policy toggles
|
||||
- **THEN** option candidates for reason/workcenter-group/package SHALL reload under the current draft context
|
||||
- **THEN** unavailable combinations SHALL NOT remain in selectable options
|
||||
|
||||
#### Scenario: Policy toggles affect option scope
|
||||
- **WHEN** user changes policy toggles (including excluded-scrap and material-scrap switches)
|
||||
- **THEN** options and query results SHALL use the same policy mode
|
||||
- **THEN** option narrowing SHALL remain consistent with backend exclusion semantics
|
||||
|
||||
#### Scenario: Invalid selected values are pruned
|
||||
- **WHEN** narrowed options no longer contain previously selected values
|
||||
- **THEN** invalid selections SHALL be removed automatically before query commit
|
||||
- **THEN** apply/query SHALL only send valid selected values
|
||||
#### Scenario: Header refresh button
|
||||
- **WHEN** the page header is rendered
|
||||
- **THEN** it SHALL include a "重新整理" button in the header-right area
|
||||
- **WHEN** user clicks the refresh button
|
||||
- **THEN** all sections SHALL reload with current filters (equivalent to "查詢")
|
||||
|
||||
### Requirement: Reject History page SHALL expose yield-exclusion toggle control
|
||||
The page SHALL let users decide whether to include policy-marked scrap in yield calculations.
|
||||
@@ -154,3 +145,53 @@ The page SHALL keep the same semantic grouping across desktop and mobile layouts
|
||||
- **WHEN** viewport width is below responsive breakpoint
|
||||
- **THEN** cards and chart panels SHALL stack in a single column
|
||||
- **THEN** filter controls SHALL remain operable without horizontal overflow
|
||||
|
||||
### Requirement: Reject History page SHALL display a loading overlay during initial data load
|
||||
The page SHALL show a full-screen loading overlay with spinner during the first data load to provide clear feedback.
|
||||
|
||||
#### Scenario: Loading overlay on initial mount
|
||||
- **WHEN** the page first mounts and `loadAllData` begins
|
||||
- **THEN** a loading overlay with spinner SHALL be displayed over the page content
|
||||
- **WHEN** all initial API responses complete
|
||||
- **THEN** the overlay SHALL be hidden
|
||||
|
||||
#### Scenario: Subsequent queries do not show overlay
|
||||
- **WHEN** the user triggers a re-query after initial load
|
||||
- **THEN** no full-screen overlay SHALL appear (inline loading states are sufficient)
|
||||
|
||||
### Requirement: Detail table rows SHALL highlight on hover
|
||||
The detail table and pareto table rows SHALL visually respond to mouse hover for improved readability.
|
||||
|
||||
#### Scenario: Row hover in detail table
|
||||
- **WHEN** user hovers over a row in the detail table
|
||||
- **THEN** the row background SHALL change to a subtle highlight color
|
||||
|
||||
#### Scenario: Row hover in pareto table
|
||||
- **WHEN** user hovers over a row in the pareto summary table
|
||||
- **THEN** the row background SHALL change to a subtle highlight color
|
||||
|
||||
### Requirement: Pagination controls SHALL use Chinese labels
|
||||
The detail list pagination SHALL display controls in Chinese to match the rest of the page language.
|
||||
|
||||
#### Scenario: Pagination button labels
|
||||
- **WHEN** the pagination controls are rendered
|
||||
- **THEN** the previous-page button SHALL display "上一頁"
|
||||
- **THEN** the next-page button SHALL display "下一頁"
|
||||
- **THEN** the page info text SHALL use Chinese formatting (e.g., "第 1 / 5 頁 · 共 250 筆")
|
||||
|
||||
### Requirement: Reject History page SHALL be structured as modular sub-components
|
||||
The page template SHALL delegate sections to focused sub-components, following the hold-history architecture pattern.
|
||||
|
||||
#### Scenario: Component decomposition
|
||||
- **WHEN** the page source is examined
|
||||
- **THEN** the filter panel SHALL be a separate `FilterPanel.vue` component
|
||||
- **THEN** the KPI summary cards SHALL be a separate `SummaryCards.vue` component
|
||||
- **THEN** the trend chart SHALL be a separate `TrendChart.vue` component
|
||||
- **THEN** the pareto section (chart + table) SHALL be a separate `ParetoSection.vue` component
|
||||
- **THEN** the detail table with pagination SHALL be a separate `DetailTable.vue` component
|
||||
|
||||
#### Scenario: App.vue acts as orchestrator
|
||||
- **WHEN** the page runs
|
||||
- **THEN** `App.vue` SHALL hold all reactive state and API logic
|
||||
- **THEN** sub-components SHALL receive data via props and communicate via events
|
||||
|
||||
|
||||
Reference in New Issue
Block a user