mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-10-08 07:01:40 +02:00
maziggy
5215ac68e9
In expanded view, PrinterQueueWidget rendered its own "Clear Plate & Start Next" button inside a yellow-bordered card whenever the plate-clear gate was up and an auto-dispatch item was queued. PR #939 added the card-level "Mark plate as cleared" button that already covers that state — and every other state (staged-only queue, empty queue, etc.) — so both buttons hit the same /clear-plate endpoint with identical optimistic-update semantics. Two controls, one action, visible together in one specific state. Remove the widget's button and its entire needsClearPlate render branch. The widget becomes a passive "Next in queue" preview linking to /queue; the card-level button remains the single plate-clear entry point. Also drop: - now-dead awaitingPlateClear / requirePlateClear / printerState props from PrinterQueueWidgetProps and the matching call site - orphaned queue.clearPlate / queue.plateReady translations from all eight locale files (queue.clearPlateSuccess stays — used by the card button's success toast) - PrinterQueueWidgetClearPlate.test.tsx (654 lines) — every test asserted the behaviour of the now-gone button; PrinterQueueWidget.test.tsx still covers the passive-link path Deliberately *not* changed: plate-status pill stays inside the Status box (lines 2664/2671/2736/2783 of PrintersPage.tsx). Compact-view (Size S) pill and icon-only clear button at :2664/:2671/:2673 untouched.
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])