Reading a manifest
Generated from engine/assets/asset_manifest_loader.h at aceb130. The text under each declaration is the header's own comment, word for word. About the reference says how these pages are made.
Audience: game code.
#include "engine/assets/asset_manifest_loader.h" · namespace labrador
read_asset_manifest
Section titled “read_asset_manifest”Reads the manifest at json_path.
The file groups assets by kind and directory, because that is how a person reads them:
{ "assets": [ { "kind": "font", "directory": "./fonts/", "names": [ "jetbrains_mono_bold_16" ] } ]}and the groups are flattened to one entry per asset, because that is how a loader walks them. Order survives the flattening: assets load in the order the file lists them.
Throws std::runtime_error naming the path if the file cannot be read or parsed, and naming the path and the offending group if the document is the wrong shape, has an unknown key or repeats a key. The document accepts only assets; each group accepts kind, directory, names and optional (default false). Asset kinds and names remain game-defined values. A manifest is hand-edited data, so every read here is checked rather than assumed (T6).
Related types
Section titled “Related types”Named in the public declarations above: AssetManifest.
In the samples and tests
Section titled “In the samples and tests”The files that include this header directly. A file can also reach it through another header.
samples/audio/smoke_test.cpp,sound_board_tests.cppsamples/components/animation_preview_null_tests.cpptests/app/content_root_tests.cpptests/assets/asset_manifest_loader_tests.cpp
Explained in
Section titled “Explained in”No guide or concept page links to this header yet.
Development documentation (unreleased). Built from Labrador aceb130 of 2026-11-20.