ux: compiler errors are derived Show dumps — no human-readable diagnostics #32

New issue

Closed

opened 2026-06-11 15:38:23 +02:00 by yorunikakeru · 0 comments

yorunikakeru commented

2026-06-11 15:38:23 +02:00

Owner

`DSL.Compile.compileResult` renders errors as `"domain error: " <> show domainErr` / `"validation error: " <> show validationErr`. End users editing /etc/frogos/configuration.hs will see:

```
validation error: AtSection (Location ProfileKind 0 "gaming") (IntraConflict "docker")
```

instead of something like:

```
profile "gaming": service "docker" is both enabled and disabled in the same section
```

Same pattern inside FromJSON parsers across IR (`fail . show`). DomainError also lacks context — `EmptyName` doesn't say which combinator received the empty name.

Suggest a `renderError :: ValidationError -> Text` / `renderDomainError` pretty-printer used by compile, keeping Show for debugging. This is the user-facing surface of the whole "invalid config doesn't compile" pitch — worth treating like UI copy.

\`DSL.Compile.compileResult\` renders errors as \`"domain error: " <> show domainErr\` / \`"validation error: " <> show validationErr\`. End users editing /etc/frogos/configuration.hs will see: \`\`\` validation error: AtSection (Location ProfileKind 0 "gaming") (IntraConflict "docker") \`\`\` instead of something like: \`\`\` profile "gaming": service "docker" is both enabled and disabled in the same section \`\`\` Same pattern inside FromJSON parsers across IR (\`fail . show\`). DomainError also lacks context — \`EmptyName\` doesn't say *which* combinator received the empty name. Suggest a \`renderError :: ValidationError -> Text\` / \`renderDomainError\` pretty-printer used by compile, keeping Show for debugging. This is the user-facing surface of the whole "invalid config doesn't compile" pitch — worth treating like UI copy.

yorunikakeru self-assigned this

2026-06-15 12:04:07 +02:00

~~yorunikakeru referenced this issue 2026-06-15 13:33:41 +02:00~~

ux: human-readable diagnostics (issue #32) #38

yorunikakeru referenced this issue from a pull request that will close it,

2026-06-15 13:35:21 +02:00

ux: human-readable diagnostics (issue #32) #38

yorunikakeru closed this issue

2026-06-15 13:35:30 +02:00

yorunikakeru referenced this issue from a commit

2026-06-15 13:35:30 +02:00

Merge pull request 'ux: human-readable diagnostics (issue #32)' (#38) from feature/issue-32-human-readable-diagnostics into main