Linting

Run lint against the file from the previous page:

bhaus-util lint user.bhaus

ok

A clean file just prints ok. lint also loads any files pulled in with INCLUDE so cross-file references resolve, but it only reports diagnostics for the file you named.

Seeing it catch something

Change the struct name to lowercase and reference a type that doesn't exist anywhere:

broken.bhaus

VERSION 0.1

STRUCT Domain/Entity/user:
    PUBLIC id: Integer
    PUBLIC manager: Domain/Entity/Manager

bhaus-util lint broken.bhaus

broken.bhaus:3:8: warning: struct name "user" should start with an uppercase letter [naming]
broken.bhaus:5:21: error: cannot resolve reference to "Domain/Entity/Manager" [unresolved-ref]

1 error, 1 warning

lint exits with code 1 when it finds at least one error-severity diagnostic. Warnings alone exit with code 0. So warnings will not fail a CI check on their own.

What gets checked

Rule	Catches
syntax	Parse errors or malformed declarations
unresolved-ref	A type, EXTENDS, IMPLEMENTS or C4 endpoint that names nothing
duplicate-decl	A declaration whose full name is declared more than once
naming	Type names should be Uppercase; function/method names lowercase
structure	VERSION must be present and be the first declaration
unknown-type	A type annotation uses the built-in Unknown type
intent-count	A function or method has 5–9 intents (warning) or 10 or more (error) and may be too large

Lint findings are useful feedback while you iterate on a design; an intermediate .bhaus file does not need to stay clean after every edit. Resolve the findings before scaffolding or using the design to update existing code. For an intent-count finding, move some behaviour into one or more additional functions or methods.

Pass --format json for machine-readable output. Use this to connect lint to an editor or a CI step:

bhaus-util lint --format json user.bhaus