Optional project settings carried by a Lmml.Bundle.

Settings are not a distinct mechanism -- they are simply an embed literally named "settings.yaml" (or "settings.json"), exactly like any other embed: @@@settings.yaml ... @@@ inline, or @settings.yaml referencing a zip entry inside a .lmmlz. This module looks that embed up, decodes it, and exposes its top-level fields as a plain map -- mirroring Lmml.Manifest's API shape.

A bundle mentioning no settings embed at all has no settings -- that is a normal, fully-supported, non-error state (load/1 returns {:ok, nil}), not something to special-case at every call site.

Encoding support

Which decoder is used depends on the settings embed's file extension:

• .json -- decoded with OTP's built-in :json (this project has no Jason dependency).

• .yaml / .yml -- decoded with a small, hand-rolled YAML-subset decoder (this project also has no YAML dependency). Support is deliberately limited to the common flat and lightly-nested shapes:

  • key: value mapping lines, where value is an integer, float, true/false, null, or a bare or quoted string;
  • nested maps written with indentation (key: followed by indented child: value lines); and
  • blank lines and full-line # comments.

  Anything outside that subset -- sequences/lists (- item), multi-line |/> block scalars, anchors/aliases, tags, etc. -- is rejected with {:error, {:unsupported_yaml, line, reason}} rather than silently mis-decoded. If a settings narrative needs richer YAML, name the embed settings.json instead.