👔 Conformetry Output
Every render target Conformetry has. It sits at
the output layer of the five-layer spine — core <- configuration <- analysis <- output <- cli — so it reads what analysis produced and turns it into text,
and runs no analysis of its own.
npm install --save-dev @conformetry/output
What it owns
| Module | Responsibility |
|---|---|
reporting | Renders structured conformance differences, and the per-instance score summary above them, as readable and actionable text |
inventory | Renders the template and instance inventory: the indent ladder, the headings, and the match percentage |
Both are rendering, and both used to live in
@conformetry/core — which is why that package
could not be a contracts leaf. They are here so that "the host composes, the
output renders" is true of conformetry the way it is of its three siblings, and
so that adding a render format has exactly one home.
Where a host gets them
ReportingModule and InventoryModule are named explicitly by whichever host
wants them. Neither is re-exported by ValidationModule: validation is an
analysis package and sits beneath this one, so it cannot reach up to hand a
renderer on.
@Module({ imports: [ReportingModule, ValidationModule] })
class EmbeddedConformetryModule {}
Paths
Paths arrive absolute, because that is the only stable way for discovery to name an instance to another process. Shortening them against a working directory is offered as a separate step rather than folded into rendering — only a host knows which directory a person is standing in.
Test
nx run conformetry-output:vitest
License
MIT — see LICENSE.
👔 Conformetry
This project was generated from the nestjs-service-project conformetry template.