Skip to content

Reference

Authoritative, exhaustive, not meant to be read start to end. API reference supplements the documentation — it never replaces it. If a reader can only find the answer to "how do I use this" here and nowhere else, that's a gap in Getting Started, Concepts, a How-to Guide, or a Package Guide — not a job Reference should grow into filling.

  • API Reference — generated from every public member's XML doc comment, one section per publishable package: Compono, Compono.XunitV3, Compono.NSubstitute, Compono.Bogus. Mechanically regenerated by .github/scripts/generate-api-reference.sh — never hand-edited, the same "generated file, don't hand-patch it" discipline this repo already applies to Compono.Generators' own output; CI fails on drift.
  • Diagnostics — every CMP code.
  • Glossary.