John Ericson 0c37a62207 Change JSON derivation format in two ways ... - Use canonical content address JSON format for floating content addressed derivation outputs This keeps it more consistent. - Reorganize inputs into nested structure (`inputs.srcs` and `inputs.drvs`) This will allow for an easier to use, but less compact, alternative where `srcs` is just a list of derived paths. It also allows for other experiments for derivations with a different input structure, as I suspect will be needed for secure build traces.		2025-11-06 15:19:44 -05:00
..
schema	Change JSON derivation format in two ways	2025-11-06 15:19:44 -05:00
build-result.md	JSON Impl and schema for BuildResult	2025-11-03 18:25:16 -05:00
build-trace-entry.md	JSON Schema for build trace entry	2025-11-03 15:59:50 -05:00
content-address.md	nlohmann::json instance and JSON Schema for ContentAddress	2025-10-27 14:47:50 -04:00
derivation.md	Change JSON derivation format in two ways	2025-11-06 15:19:44 -05:00
deriving-path.md	JSON Schema for DerivedPath	2025-10-24 12:08:00 -04:00
fixup-json-schema-generated-doc.sed	nlohmann::json instance and JSON Schema for ContentAddress	2025-10-27 14:47:50 -04:00
hash.md	Convert store path info JSON docs to formal JSON Schema, and test	2025-10-28 23:28:16 -04:00
index.md	Rename doc/manual{src -> source}	2024-10-14 11:21:24 -04:00
json-schema-for-humans-config.yaml	Add JSON Schema infrastructure, use for Derivation	2025-10-16 17:24:18 -04:00
meson.build	Change JSON derivation format in two ways	2025-11-06 15:19:44 -05:00
store-object-info.md	Convert store path info JSON docs to formal JSON Schema, and test	2025-10-28 23:28:16 -04:00
store-path.md	Convert store path info JSON docs to formal JSON Schema, and test	2025-10-28 23:28:16 -04:00