Command reference
zincite fmt, zincite lint and zincite query use the same options as
zincite-fmt, zincite-lint and zincite-query, respectively. Installed help
lists the accepted options:
zincite --helpzincite fmt --helpzincite lint --helpzincite query --helpInput and output
Section titled “Input and output”Formatting and linting accept files, directories or stdin. With no input or -,
they read stdin; do not mix stdin with file inputs. --stdin-filepath PATH
selects language mode and the configuration lookup path. A .dzn path selects
data syntax; plain stdin uses model syntax. Directory discovery includes hidden
and Git-ignored .mzn and .dzn files and skips .git.
Formatter stdout mode accepts one input. Multiple files require --check or
--write; directories support --check only. Formatter diagnostics go to stderr.
Lint diagnostics go to stderr; ordinary analysis preserves files.
Queries accept one query and at most one file or -; omitted input reads stdin.
The query reference defines pipeline output and
semantic model loading. Query diagnostics go to stderr.
Explicit writes
Section titled “Explicit writes”Formatter --write and query --write require explicit regular files and
refuse symlinks. Lint uses --fix with its own fix eligibility and write
restrictions. Formatter --check and
--write are mutually exclusive; query --diff and --write are mutually
exclusive. A failing formatter input is not written; other independent files
continue. Query write validates the complete candidate and checks the original
bytes again before replacing the file. Writes retain file permissions.
Exit codes
Section titled “Exit codes”| Code | Formatter | Linter | Query |
|---|---|---|---|
0 |
Formatting succeeded; check found no changes | No unsuppressed warnings or errors | Complete result |
1 |
Check found formatting changes | Unsuppressed warnings | Incomplete semantic report or reduction candidate |
2 |
Input, syntax, configuration, directive, usage or I/O error | Input, syntax, settings, directive, usage, dependency or I/O error | Query, input, model, usage or I/O error |
Errors take precedence across formatter/linter inputs. A query’s empty fragment selection succeeds with no source; its count is 0. Lint limitations alone retain status 0 or 1. Status 0 does not establish complete semantic coverage.