• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Rotorsoft / act-root / 34358860953
100%

Build:
DEFAULT BRANCH: master
Ran 09 Sep 2026 01:45PM UTC
Jobs 1
Files 118
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

09 Sep 2026 01:42PM UTC coverage: 100.0%. Remained the same
34358860953

push

github

web-flow
feat(act-diagram): export the pipeline stages the IDE plugins need (#1659)

* docs(act-diagram): document the exports the package actually has

The README's Functions table listed ten entries; src/index.ts exports
two of them. The other eight — extractModel, buildModel, navigateToCode,
topoSort, computeLayout, parseMultiFileResponse, stripFences,
deriveProjectName — exist only under internal snake_case names and are
never re-exported, so the "Bring-your-own pipeline" snippet documenting
them did not compile. Same shape as #1621 on act-http/webhook, and
larger.

Re-exporting them would have been the other way out, but the package
parses Act source and ActDiagram owns that pipeline end to end. Handing
out the individual stages is public surface this tool does not need, so
the table now lists validate and emptyModel, says plainly that the rest
is internal, and the pipeline snippet is gone rather than made to work.
A Types section replaces the exports that were only ever documented by
that snippet's imports.

Closes #1650

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QPx2Qu7ZHDTSpoWYJvX4RJ

* docs(act-diagram): say why the pipeline stages stay internal, not that they always will

The first pass declared "no plan to add one", which is a roadmap
commitment rather than a fact about the code, and act-diagram has real
IDE consumers — the Neovim and VS Code plugins — whose needs are not
mine to foreclose in a README.

What is a fact: the stages are absent from the exports map, so they
cannot be imported even by path, and the plugins drive the diagram
through the component and the postMessage protocol instead. The section
now says that, names the plugins as the case the component surface
exists for, and points a host that genuinely needs a stage at an issue
and the RFC gate rather than at a deep import.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https:... (continued)

4353 of 4353 branches covered (100.0%)

Branch coverage included in aggregate %.

9419 of 9419 relevant lines covered (100.0%)

1186.47 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34358860953.1 09 Sep 2026 01:45PM UTC 118
100.0
GitHub Action Run
Source Files on build 34358860953
  • Tree
  • List 118
  • Changed 1
  • Source Changed 1
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #34358860953
  • 52e79f6e on github
  • Prev Build on master (#34356651662)
  • Next Build on master (#36345368888)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc