Value Members

1.  object HOCON

   HOCON/YAML backend for the cfg protocol.

   HOCON/YAML backend for the cfg protocol.

   Load one or more HOCON or YAML files and receive a Node.IMap[Id.Root] ready for decoding.

   Merging and substitution

   When multiple URLs are supplied they are merged in order — later files take precedence over earlier ones (last-wins), following Typesafe Config's withFallback semantics. After merging, ConfigFactory.load is called so that variable substitutions are resolved before the tree is returned.

   YAML support

   YAML files are parsed via io.h8:typesafe-config-yaml with stringsOnly = true. This aligns with the protocol contract: Node.IScalar always carries a raw string, and type conversion is the decoder's responsibility.

   HOCON and JSON files, however, go through Typesafe Config's own parser, which infers types (booleans, numbers, lists, etc.) before this library can see the values. Scalars are then recovered by calling unwrapped.toString on the parsed Java object, so the string stored in Node.IScalar may not match the original text in the file exactly (e.g. a number written as 1e5 may come back as 100000.0).

   YAML tags are not propagated; the tag field is always None.

   Thread safety

   The shared ConfigLoader is stateless after construction and safe for concurrent use.