src/ledger/render.bend checks

a key line, or nothing at all when the value is empty, so an absent tag, entry or bin leaves no trace

a key line whose value is written bare, as a TOML boolean is, or nothing at all when the value is empty

true when the tree is committed, and nothing when it is not, so the key is absent rather than written as an empty string. It is written bare: in TOML vendor = "true" is a string, and a reader other than ez, such as nix's builtins.fromTOML, would take it for one. ez reads both spellings.

the keys a source contributes

one [deps.<name>] section

every dependency, in the order the ledger holds them

one [tools.<name>] section. No hash: a tool is not a package.

every pinned CLI, in the order the ledger holds them

the ledger as ez assembles it, in the TOML ez wrote before eztoml 0.4

the ledger as an ez.toml: ez's text, written as eztoml writes it

a ledger that was read, as an ez.toml; an unreadable one renders as nothing, so a failed read can never overwrite a good file with a guess

a dependency kept or dropped

every dependency but the one named

the ledger with a dependency added, replacing any of the same name, so adding twice is the same as adding once

the ledger with a dependency dropped

a git source with its tree committed

a source that keeps a vendor bit the ledger already set, or is left as given

a dependency added again keeps the vendor = true its entry already had. The command line has no way to say it, so a re-add that dropped it would drop the tree from the allowlist without anyone having asked.

the ledger with a dependency added, keeping the vendor bit of the entry it replaces

whether a text holds no copy of a char

whether a name or value can be written as it is: it holds no ", no \ and no newline. The pinned eztoml reader (v0.1.0) neither writes nor reads escapes, a newline would end the line, and a quote or a backslash would make the file mean something else to every other TOML reader, nix's among them.

whether a source reads back as itself. A git source names its repo and the directory its paths are written from: the reader takes a section with no git for a hub package and one with no root for the top of the checkout.

whether a dependency does: it has a hash, which the reader asks every dependency for, and every name and value is clean

whether every dependency does

whether a pinned CLI's source does. A tool is never imported, so the reader keeps no hub name for one, and one written with a name would read back without it.

whether a pinned CLI does

whether every pinned CLI does

whether a ledger can be written so that it reads back as itself (EZ-LED-4): every name and value is clean, publish-as and version among them, every dependency has a hash, and every git source names its repo and its root. Every command that writes ez.toml refuses a ledger that is not, so every ledger ez writes is one of these.

why a ledger that is not renderable is not written