fix(ui): remove vestigial ref, fix stale MeshMap test mock
Web5ConnectedNodes.vue declared nodesContainerRef but never consumed it (the controller-nav system scans [data-controller-container] globally, no other view uses a per-component ref for it) — broke the vue-tsc build. MeshMap.test.ts's mocked mesh store predated federatedPositions (added earlier this session for the Mesh Map federated-node feature) and crashed on mount. Found live merging PR#67 (reticulum) + UI/UX work + archy-openwrt into main for a combined fleet deploy. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
27093e682f
commit
9f52e81471
@@ -4,6 +4,7 @@ import MeshMap from '../MeshMap.vue'
|
||||
|
||||
const meshState = vi.hoisted(() => ({
|
||||
nodePositions: new Map(),
|
||||
federatedPositions: new Map(),
|
||||
peers: [],
|
||||
status: null,
|
||||
deadmanStatus: null,
|
||||
@@ -33,6 +34,7 @@ vi.mock('leaflet', () => ({
|
||||
describe('MeshMap', () => {
|
||||
beforeEach(() => {
|
||||
meshState.nodePositions.clear()
|
||||
meshState.federatedPositions.clear()
|
||||
meshState.peers = []
|
||||
meshState.status = null
|
||||
meshState.deadmanStatus = null
|
||||
|
||||
Reference in New Issue
Block a user