pub struct Options {
pub sources: Vec<Source>,
pub formats: Vec<FormatSpec>,
pub recursive: bool,
pub flat: bool,
pub dot_key: bool,
pub case_sensitive: bool,
pub order: Order,
pub tree: bool,
pub auto_files: bool,
pub ignore_unknown_ext: bool,
}Expand description
All loader options.
Plain data on purpose: set the fields you care about and take the rest
from ..Options::default().
Fields§
§sources: Vec<Source>The ordered config sources; later sources override earlier ones.
Default: the config folder under the current working directory.
formats: Vec<FormatSpec>Which formats to read and which extensions each one claims. The list carries no override-order semantics — it only builds the extension→format mapping (if several entries claim the same extension, the last entry wins the claim). Override order between files is decided by filename alone; see the merge rules in README.md.
recursive: boolScan subdirectories. Default false.
flat: boolWhen recursive, ignore subfolder paths instead of turning them
into nested keys. Default true — merge mode flattens; nesting
by folder structure is tree mode’s job (or set flat: false).
dot_key: boolTreat dotted env/table keys as nested paths: a.b.c becomes
{ "a": { "b": { "c": … } } }. Default true.
case_sensitive: boolCase-sensitive key merging. Default true; when false, keys are
normalized to lowercase. (File-extension matching is always
case-insensitive and unrelated to this option.)
order: OrderLoad order inside a folder — in merge mode and in tree mode
(where it decides key collisions like a.yml vs a folder a/).
tree: boolTree mode (requires the tree feature): instead of merging a
folder’s files into one value, every subfolder becomes a key and
every file becomes a key named after the file (extension
stripped), holding that file’s parsed content. a/b.json = {c:1}
and d.json = {a:123} load as {a: {b: {c: 1}}, d: {a: 123}}.
recursive, flat and order only apply when this is false.
Default false.
auto_files: boolTree mode: parse files without an extension by running the
table auto detection over the (trimmed) file content — the same
feature-gated guesses, so a/blabla containing 1.1.1.1 becomes
an IPv4 value when the ipv4 feature is on, a string otherwise.
When false, extension-less files fall under
ignore_unknown_ext. (Named auto_files to keep it apart from
the table auto format id it reuses.) Default true.
ignore_unknown_ext: boolTree mode: skip files whose extension no active format claims
(true), or error on them (false). Default true. (In merge
mode unclaimed files are always skipped.)