Quick-fixes

When the validator flags certain problems, the editor can offer to fix them on the spot. These quick-fixes are deliberately narrow — they handle a few specific, well-defined cases where the correct change is obvious — so think of them as convenient one-click tidy-ups, not a general auto-correct. For anything broader, the headline tool is the bulk transform rule builder (see below).

Where a fix shows up

A fixable diagnostic carries its fix with it. When you reach the marked spot — hover the underline, or open the diagnostic — the message is followed by a Proposed fixes: heading and an underlined link for each available fix. Click the link and the change is made for you.

For a FILE reference you can also bring up the fix from the file tooltip: hover the path and, if there’s a fix to offer, the tooltip shows it as an action below the file’s details.

What can be fixed

Most quick-fixes today centre on FILE references — the paths that link a record to a photo, document, or other file in your project. When a path doesn’t match a file on disk, you may see:

• Try to resolve this file reference… — when the path doesn’t point to an existing file, the editor tries to locate the file you most likely meant and repoint the reference to it.
• Fix case of this reference — when a file exists but the path’s capitalisation doesn’t match it (Photo.JPG vs. photo.jpg), this corrects the case so the reference resolves. Case mismatches are easy to miss because they work on some systems and break on others.

An unknown tag — a non-standard tag the version’s grammar doesn’t define, written without the leading underscore that marks a deliberate custom tag — offers two fixes instead. Both hand off to the transform panel (see below) so you can preview which nodes they touch before applying:

• Delete all <TAG> nodes… — remove every node using that tag, across the whole file.
• Convert <TAG> to custom tag _<TAG>… — rename it to the underscore form, telling the checker the tag is intentional so the diagnostic goes away.

Where no quick-fix is offered, the diagnostic still tells you what’s wrong and points you to the spot — and you can always look the structure up in the spec viewer to understand it.

Limited by design

Quick-fixes cover a small, specific set of problems — they are not a sweep that cleans up a whole file. Don’t expect a fix to appear for most diagnostics. They’re a shortcut for the cases where the fix is unambiguous, nothing more.

For sweeping changes: bulk transforms

When the change you want isn’t a one-off — renaming a tag across hundreds of records, reshaping a structure everywhere it occurs, cleaning up a recurring data-entry pattern — reach for the bulk transform rule builder. You describe the change once and apply it everywhere it matches, with a live preview before you commit. That bulk path, not inline quick-fixes, is the main way Linea Codex helps you fix problems at scale.

The two connect: some quick-fixes hand off to the transform panel, opening it pre-loaded with a rule you can review and run — so a fix that looks like a single spot-fix can become a project-wide one when that’s what the situation calls for.

---

Next: how the editor guards the managed links behind a half-built relative — Skeleton-link protection →.