John Ericson
12760756bb
nlohmann::json instance and JSON Schema for MemorySourceAccessor
...
As documented, this for file system objects themselves, since
`MemorySourceAccessor` is an implementation detail.
2025-11-06 13:55:46 -05:00
John Ericson
147e183c68
Merge pull request #14426 from obsidiansystems/json-schema-build-result
...
JSON Impl and schema for BuildResult
2025-11-06 18:40:35 +00:00
Jörg Thalheim
daace78239
Merge pull request #14425 from obsidiansystems/json-schema-build-trace
...
JSON Schema for build trace entry
2025-11-06 18:06:57 +00:00
Robert Hensing
ae15d4eaf3
Fix links in the manual
2025-11-04 00:31:46 +01:00
John Ericson
389bcba97a
JSON Impl and schema for BuildResult
2025-11-03 18:25:16 -05:00
John Ericson
144c66215b
JSON Schema for build trace entry
...
Note, starting to make progress on #11895 by calling it this in the
manual.
2025-11-03 15:59:50 -05:00
John Ericson
72d0f7b619
Document "hash derivation quotiented", resolution, and build trace
...
Progress on #13405 , which asks for an explicit characterisation of the
equivalence relation like the one given here.
Also progress on #11895 , because we're using the term "build trace
entry" instead of "realisation".
Mention #9259 , a future work item.
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2025-11-03 15:18:18 -05:00
John Ericson
c2609df08c
Better JSON schema for derivation outputs
...
It now uses a `oneOf` and properly models each type of output
(corresponding to each type of derivation) separately.
2025-10-30 17:05:00 -04:00
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
John Ericson
c67966418f
Create JSON Schema for Store Paths
...
We immediately use this in the JSON schemas for Derivation and Deriving
Path, but we cannot yet use it in Store Object Info because those paths
*do* include the store dir currently.
2025-10-28 17:22:51 -04:00
John Ericson
be2572ed8d
Make inputDrvs JSON schema more precise
...
It now captures the stable non-recursive format (just an output set) and
the unstable recursive form for dynamic derivations.
2025-10-28 17:22:30 -04:00
John Ericson
91b69e9e70
nlohmann::json instance and JSON Schema for ContentAddress
...
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2025-10-27 14:47:50 -04:00
John Ericson
8d338c9234
JSON Schema for DerivedPath
...
Note that this is "deriving path" in the manual -- the great sed of the
code base to bring it in sync has yet to happen yet.
2025-10-24 12:08:00 -04:00
John Ericson
5e7ee808de
nlohmann::json instance and JSON Schema for Hash
...
Improving and codifying our experimental JSON interfacing.
Co-Authored-By: Robert Hensing <robert@roberthensing.nl>
2025-10-20 15:21:07 -04:00
Robert Hensing
c92ba4b9b7
Add titles in JSON schemas
...
This way, the description isn't rendered in the tables of contents,
leading to no more formatting errors.
2025-10-17 21:53:29 +02:00
Robert Hensing
01b001d5ba
Add JSON Schema infrastructure, use for Derivation
...
For manual, and testing formats
2025-10-16 17:24:18 -04:00
