John Ericson 6280905638 Convert store path info JSON docs to formal JSON Schema, and test ... This continues the work for formalizing our current JSON docs. Note that in the process, a few bugs were caught: - `closureSize` was repeated twice, forgot `closureDownloadSize` - `file*` fields should be `download*`. They are in fact called that in the line-oriented `.narinfo` file, but were renamed in the JSON format.		2025-10-28 23:28:16 -04:00
..
content-address-v1	nlohmann::json instance and JSON Schema for ContentAddress	2025-10-27 14:47:50 -04:00
content-address-v1.yaml	nlohmann::json instance and JSON Schema for ContentAddress	2025-10-27 14:47:50 -04:00
derivation-v3.yaml	Create JSON Schema for Store Paths	2025-10-28 17:22:51 -04:00
deriving-path-v1	JSON Schema for DerivedPath	2025-10-24 12:08:00 -04:00
deriving-path-v1.yaml	Create JSON Schema for Store Paths	2025-10-28 17:22:51 -04:00
hash-v1	nlohmann::json instance and JSON Schema for Hash	2025-10-20 15:21:07 -04:00
hash-v1.yaml	nlohmann::json instance and JSON Schema for ContentAddress	2025-10-27 14:47:50 -04:00
nar-info-v1	Convert store path info JSON docs to formal JSON Schema, and test	2025-10-28 23:28:16 -04:00
store-object-info-v1	Convert store path info JSON docs to formal JSON Schema, and test	2025-10-28 23:28:16 -04:00
store-object-info-v1.yaml	Convert store path info JSON docs to formal JSON Schema, and test	2025-10-28 23:28:16 -04:00
store-path-v1	Create JSON Schema for Store Paths	2025-10-28 17:22:51 -04:00
store-path-v1.yaml	Create JSON Schema for Store Paths	2025-10-28 17:22:51 -04:00