# Keeping your code neat

[Programming guides](README.md)

Formatting makes spacing and indentation consistent so code is easier to read. It does not decide whether your game rules are correct.

The formatter normalizes:

- four spaces per block level;
- multiline delimiter continuation indentation;
- spacing around operators, commas, and map colons;
- inline-comment separation;
- trailing whitespace and trailing blank lines;
- one final newline for a non-empty file.

It preserves source locale, identifiers, literal spellings, comments,
command-call versus parenthesized-call style, and the file's line-ending style.
Formatting is idempotent.

```shell
pliro fmt program.pliro
pliro fmt --check program.pliro
pliro fmt --stdout program.pliro
```

For `.bipli`, [CLI](../concepts/command-line.md) formatting atomically replaces only the embedded entry source
and preserves the manifest, other sources, and assets. `--check` and `--stdout`
never write; `--check` exits unsuccessfully when formatting changes are needed.
Internal blank-line counts are preserved.

## Related entries

[Syntax and values](../syntax/README.md) · [Built-ins](../builtins/README.md) · [Programming guides](README.md)