dangernoodle-io / ouroboros / 28993658956
92%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 41
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 85.19% (+0.9%) from 84.242%
28993658956

push

github

web-flow 
feat: roadmap component/epic axes, states, reordering (#91)

- rename Item.Lane -> Item.Epic (json epic,omitempty): an epic is a
  backlog item (EPIC: convention); component (structural) and epic are
  now two independent single-valued grouping axes, each rejecting a
  list/second value on write
- migration v12: items.epic column (additive, NULL-safe default '')
- canonicalize-on-save is pure per-section stable Position sort; axis
  grouping (component vs epic) moves to render time (groupByAxis),
  since a section can now be rendered grouped by either axis
- RenderMarkdown(rm, by, epicLabels, blockedEpics): by picks the
  grouping axis (component default, or epic); the other axis renders
  as an inline chip, using the SAME resolved epic label as the
  epic-grouped header (falls back to the raw id identically); an epic
  group header shows the resolved backlog item title (EPIC: prefix
  stripped) and a blocked-epic marker (wired for a later phase,
  unpopulated for now)
- getRoadmap/roadmap CLI show gain by/component/epic; roadmap
  add/update gain epic; backlog create/update gain the single-valued
  epic field (and component now shares the same scalar enforcement),
  surfaced in list/get
- section Position invariant: a section is either LEGACY (all-0,
  sorts by slice/add order) or DENSE (1..N mirroring slice order),
  enforced by every op that changes membership or order:
  - ReorderItem/MoveItem's position is a 0-based target index: a
    position write physically splices the item to that index and
    densely renumbers the whole section, so index 0 always sorts
    first -- even when every sibling is still at the legacy Position 0
  - AddItem's position is presence-signaled the same way (item.Position
    is never read as an ordering input -- only an explicit variadic
    position controls placement); with no position, a new renumberIfDense
    helper keeps a DENSE section's invariant intact (new item sorts
    last) while leaving a LEGACY section ... (continued)

3618 of 4247 relevant lines covered (85.19%)

1.0 hits per line

Coverage Regressions

Lines Coverage ∆ File
41
84.75
 1.69% backlog/items.go
15
94.9
 -5.1% cli/roadmap.go
12
96.66
 1.83% roadmap/roadmap.go
9
69.61
 0.0% store/store.go
4
90.45
 0.85% app/handlers_backlog.go
2
99.33
 -0.67% app/handlers_roadmap.go
Jobs
ID Job ID Ran Files Coverage
1 28993658956.1 41
85.19
 GitHub Action Run
Source Files on build 28993658956