DashBoard/spec.md at bf7285fb51c5d398e1347c8b0742900ff519bd8a

Files

egg bf7285fb51 feat(qc-gate): add QC-GATE real-time LOT status report as first pure Vue 3 + Vite page

Introduce QC-GATE station monitoring with stacked bar chart and filterable LOT table,
using Vue 3 SFC + ECharts via npm. Establishes the pure Vite page architecture pattern
(no Jinja2) for future page migration. Also removes stale design files and README.mdj.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-09 13:06:59 +08:00

2.2 KiB

Raw Blame History

ADDED Requirements

Requirement: Pure Vite pages SHALL be served as static HTML

The system SHALL support serving Vite-built HTML pages directly via Flask without Jinja2 rendering.

Scenario: Serve pure Vite page

WHEN user navigates to a pure Vite page route (e.g., /qc-gate)
THEN Flask SHALL serve the pre-built HTML file from static/dist/ via send_from_directory
THEN the HTML SHALL NOT pass through Jinja2 template rendering

Scenario: Page works in portal iframe

WHEN the pure Vite page is loaded inside the portal iframe
THEN the page SHALL render correctly within the iframe context
THEN CSP frame-ancestors 'self' SHALL allow the embedding

Requirement: Vite config SHALL support Vue SFC and HTML entry points

The Vite build configuration SHALL support Vue Single File Components alongside existing vanilla JS entries.

Scenario: Vue plugin coexistence

WHEN vite build is executed
THEN Vue SFC (.vue files) SHALL be compiled by @vitejs/plugin-vue
THEN existing vanilla JS entry points SHALL continue to build without modification

Scenario: HTML entry point

WHEN a page uses an HTML file as its Vite entry point
THEN Vite SHALL process the HTML and its referenced JS/CSS into static/dist/
THEN the output SHALL include <page-name>.html, <page-name>.js, and <page-name>.css

Scenario: Chunk splitting

WHEN Vite builds the project
THEN Vue runtime SHALL be split into a vendor-vue chunk
THEN ECharts modules SHALL be split into the existing vendor-echarts chunk
THEN chunk splitting SHALL NOT affect existing page bundles

Requirement: Pure Vite pages SHALL handle API calls without legacy MesApi

Pure Vite pages SHALL use the existing frontend/src/core/api.js module for API communication without depending on the global window.MesApi object from _base.html.

Scenario: API GET request from pure Vite page

WHEN a pure Vite page makes a GET API call
THEN the call SHALL use the apiGet function from core/api.js
THEN the call SHALL work without window.MesApi being present

2.2 KiB Raw Blame History