Table of Contents

Configuration guides

Recipe-style walk-throughs for the Configuration topic - Bodu.Text.Configuration, the layered EditorConfig-style parser and resolver, and Bodu.Extensions.Configuration.Text, its bridge into Microsoft.Extensions.Configuration.

If you are new to the topic, start with the Configuration overview for the pipeline and package boundaries, and the Configuration concepts glossary for the shared vocabulary (profile, preamble, glob-anchored section, layered resolution, view, source, provider, reload token).

Bodu.Text.Configuration

Parse a configuration document under one of the four profiles (Bodu, EditorConfigCompatible, Strict, Relaxed), resolve it for a target path, and read typed values back out.

Overview

Namespace map, the parse → resolve → view pipeline, and where each guide fits.

Parsing and profiles

ConfigurationDocument.Parse, ConfigurationParseOptions, and the four profile presets - inline comments, duplicate handling, length limits.

Views and resolution

Resolve → ConfigurationView: glob matching against a target path, key projection, typed getters, missing-key fallbacks.

Diagnostics

The structured diagnostic surface - modes, severities, and the full ConfigurationDiagnosticCode catalogue.

Bodu.Text.Configuration API reference

Bodu.Extensions.Configuration.Text

Surface a parsed and resolved document through the standard IConfiguration pipeline that ASP.NET Core and Generic Host already consume.

Overview

Namespace map - builder extensions, file and stream sources and providers, DI options helpers.

Configuration sources

AddTextConfigurationFile / AddTextConfigurationStream, the conventional file probe, reload-on-change, target-path anchoring, and IOptions<T> binding.

Bodu.Extensions.Configuration.Text API reference

Suggested reading path

  1. Parsing and profiles - get a document out of source text and pick the right profile.
  2. Views and resolution - project the document for a target path and read typed values.
  3. Diagnostics - handle user-authored input that may not be canonical.
  4. Configuration sources - hand the result to Microsoft.Extensions.Configuration when you host there.

See also