Skip to content

Reload Handles

Reference

Reload handles let you refresh config safely without discarding the last valid runtime state, even when the file also merges defaults or runs migrations.

Simple unmanaged reload handle for one typed YAML file.

Required

Simple unmanaged bundle handle across multiple files.

Optional

Managed reload handle with merge, migration, and metadata.

Required

Managed bundle handle for module settings plus optional lang.

Optional

current object

Returns the last valid decoded runtime value.

Required

reload() object

Reloads the handle while preserving the previous good runtime value on failure.

Required

Managed handle operation that reloads, merges, migrates, and returns reports.

Optional

Simple reload results use DaisyReloadResult<T>.

Managed reload results use:

  • DaisyManagedReloadResult<T>
  • DaisyManagedBundleReloadResult<T>

Those managed result types add migration reports because the managed path can create files, merge missing keys, and advance config_version before decoding.