Issues

check: qualified references to an imported module's `config` warn `unknownName`, contradicting the documented "Config parameter references" semantics; `deferred` names are likewise unresolvable

#89

· yenda opened

on Aug 13, 2026

check: only the first statement of an `ensures:` block is exported to importers — later emissions produce false `unknownName` on every consumer

#88

· yenda opened

on Aug 13, 2026

check: a suppressed `allium.use.unresolvedPath` silently disables all name checking through that alias (exit 0 on arbitrary dangling references)

#87

· yenda opened

on Aug 13, 2026

Event Sourcing semantics with Allium?

#85

· tburny opened

on Aug 11, 2026

Spec AST is incomplete

#57

· henrygarner opened

on Jul 1, 2026

Consider `bun build --compile` for `allium-lsp` distribution

#17

· tburny opened

on Apr 26, 2026

Add a Nix flake

#16

· tburny opened

on Apr 26, 2026

Navigation Menu

Uh oh!

All issues

check: qualified references to an imported module's `config` warn `unknownName`, contradicting the documented "Config parameter references" semantics; `deferred` names are likewise unresolvable

check: only the first statement of an `ensures:` block is exported to importers — later emissions produce false `unknownName` on every consumer

check: a suppressed `allium.use.unresolvedPath` silently disables all name checking through that alias (exit 0 on arbitrary dangling references)

Event Sourcing semantics with Allium?

Spec AST is incomplete

Consider `bun build --compile` for `allium-lsp` distribution

Add a Nix flake

Uh oh!

Search results

check: qualified references to an imported module's config warn unknownName, contradicting the documented "Config parameter references" semantics; deferred names are likewise unresolvable

check: only the first statement of an ensures: block is exported to importers — later emissions produce false unknownName on every consumer

check: a suppressed allium.use.unresolvedPath silently disables all name checking through that alias (exit 0 on arbitrary dangling references)

Event Sourcing semantics with Allium?

Spec AST is incomplete

Consider bun build --compile for allium-lsp distribution

Add a Nix flake

check: qualified references to an imported module's `config` warn `unknownName`, contradicting the documented "Config parameter references" semantics; `deferred` names are likewise unresolvable

check: only the first statement of an `ensures:` block is exported to importers — later emissions produce false `unknownName` on every consumer

check: a suppressed `allium.use.unresolvedPath` silently disables all name checking through that alias (exit 0 on arbitrary dangling references)

Consider `bun build --compile` for `allium-lsp` distribution