Refinements as versioned specs (UI for backend#12) #7

Closed
opened 2026-10-25 12:29:39 +00:00 by Gilles · 0 comments
Owner

Frontend half of thierryade/backend#12: refinements become versioned specs refining another spec (Spec.refines), absences become refinement versions (is_absence), and a reopen cascades pending decisions (keep / new version / absence) down the refinement tree.

  • Drop every use of /api/refinements/ and of refinement attachment/test targets.
  • "Par raffinage" tree built from Spec.refines: each spec once under the spec it refines, absences as dashed lines, missing child places flagged, pending decisions tagged.
  • Spec detail: "Raffine" link, former -R- codes, decision box on a pending draft, new refinement / documented absence per child place.
  • "Par emplacement": creating a spec below the root requires picking the refined spec.
Frontend half of thierryade/backend#12: refinements become versioned specs refining another spec (`Spec.refines`), absences become refinement versions (`is_absence`), and a reopen cascades pending decisions (keep / new version / absence) down the refinement tree. - Drop every use of `/api/refinements/` and of refinement attachment/test targets. - "Par raffinage" tree built from `Spec.refines`: each spec once under the spec it refines, absences as dashed lines, missing child places flagged, pending decisions tagged. - Spec detail: "Raffine" link, former `-R-` codes, decision box on a pending draft, new refinement / documented absence per child place. - "Par emplacement": creating a spec below the root requires picking the refined spec.
Sign in to join this conversation.
No description provided.