format.changes_required
A file jadpo fmt --check read isn't laid out as jadpo fmt would write it.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
Jadpo has one layout, which jadpo fmt writes, so equivalent code always
looks the same and a diff shows only real changes. jadpo fmt --check
changes nothing: it is the check CI runs, and fails when a file differs
from what the formatter would write, pointing at the first place it
differs. The edit it would make is in --json, for an agent to apply.
What it looks like
A type written with two spaces of indentation, where the formatter writes four:
cat > domains/tasks/types/task_title.jadpo <<'EOF2'/// What a task is called.type TaskTitle = Text { max_length: 200}EOF2jadpo fmt --check
error This file isn't formatted
--> domains/tasks/types/task_title.jadpo:3:3
|3 | max_length: 200 | ^ the formatter changes this line
- reason
jadpo fmtlays this file out differently from here on.- next
- Run
jadpo fmtto format it (agent) - rule
- format.
changes_ required - help
- https://jadpo.
dev/docs/errors/format. changes_ required
(agent) at the end of the next: line means your coding agent can make the fix itself.
How to fix it
If the file should be in Jadpo's layout, as every file is, format it:
jadpo fmtEvery file is rewritten in the one layout, and jadpo fmt --check then
passes. An editor with the Jadpo extension formats each file as it
saves it.
Related
Markdown for agents: /docs/errors/format.changes_required.md.Built from Jadpo main at aee2e8f.