plans(server): a board you delete is back at the next boot #2318
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2318
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1120-2137"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds
docs/plans/board-lifecycle.md. Plans only, no code.Measured on
5da9cc49by running the real server against a scratchPF_DATA:DELETE /api/topologies/lab-keepanswers{ok:true}and removes the map entry;lab-keep.jsonstays on disk andloadSavedTopologies()brings the board back on the next boot (server/index.js:844, :200-224).DELETEof a board that never existed answers 200.DELETE— onlyrmrecovers it.GET /api/topologiesis{ids}only;savedAtis written at :158 and read nowhere.POSTon an occupied name answers 201.DELETEnever callsbroadcast(), so a second tab keeps painting a deleted board; the client is pinned toconst TOPO = 'default'(web/app.js:4) and never lists boards.DELETE.Six ordered steps (S/S/S/S/S/S-M) plus one M fenced as needs-Jay (a board surface in the UI). Closes no open issue; the queue is #803 and #130.
Deliberately left out: rename/duplicate, the fixed export filename, document-version migration, and the
fullState()-twice cost.