diff options
Diffstat (limited to '.github')
| -rw-r--r-- | .github/instructions/frontend.instructions.md | 2 | ||||
| -rw-r--r-- | .github/instructions/rust-backend.instructions.md | 12 |
2 files changed, 1 insertions, 13 deletions
diff --git a/.github/instructions/frontend.instructions.md b/.github/instructions/frontend.instructions.md index 7ce27c0..997d6c1 100644 --- a/.github/instructions/frontend.instructions.md +++ b/.github/instructions/frontend.instructions.md @@ -8,7 +8,7 @@ applyTo: # Frontend Data Flow - Keep data fetching in hooks or small container components. `Path.js`, `Info.js`, `Log.js`, and `Options.js` wire backend data into display components; `usePolling.js` and `useSSE.js` own subscription cleanup. -- Preserve the current backend contract unless the task explicitly coordinates with backend changes. The frontend is hardcoded to `http://localhost:8000`, not the Rust backend on `:8080`. +- Preserve the current backend contract unless the task explicitly coordinates with backend changes. The frontend is hardcoded to `http://localhost:8000`. - Keep display components render-focused. Formatting, icons, animation, and simple click handlers belong near `DataDisplay.js`, `InfoDisplay.js`, and `LogComponent.js`; reusable network behavior belongs in hooks. - Stick to the current stack: React function components, Tailwind utility classes, and local CSS files. Do not introduce a new state library, routing layer, or styling system unless asked. - If you add polling or SSE behavior, always include cleanup and keep the return shape simple for the consuming component.
\ No newline at end of file diff --git a/.github/instructions/rust-backend.instructions.md b/.github/instructions/rust-backend.instructions.md deleted file mode 100644 index 719544a..0000000 --- a/.github/instructions/rust-backend.instructions.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -description: "Use when editing the Rust backend, Actix handlers, EVE service client, or pathfinding and market modules under rust_backend/src. Covers experimental status, service boundaries, and integration gaps." -name: "Rust Backend Boundaries" -applyTo: "rust_backend/src/**/*.rs" ---- -# Rust Backend Boundaries - -- Treat `rust_backend/` as an experimental rewrite, not a drop-in replacement for the Python backend. The current frontend does not target it. -- Keep `main.rs` as a thin Actix entrypoint. Shared state and polling belong in `manager.rs`; ESI and OAuth transport belongs in `eve_service.rs` and `eve_api.rs`. -- Keep `pathfinding/` and `market/` self-contained. Avoid pulling HTTP concerns, UI assumptions, or Actix types into those modules. -- Do not assume feature parity with the Python backend. If a task requires frontend integration, add the missing routes, payload shapes, and CORS deliberately rather than silently reusing Python assumptions. -- Rust runtime work depends on local OAuth env vars (`CLIENT_ID`, `CLIENT_SECRET`, `CHARACTER_ID`, `REDIRECT_URL`) and `token.json`. Preserve that flow unless the task is specifically about changing auth setup.
\ No newline at end of file |