Skip to content

Alpha Notes and Limitations

Thinai is in alpha. The first release is 0.1.0-alpha.1. Syntax and language-service behavior may still change between releases. The examples, grammar, and validation rules in this documentation describe the current alpha behavior.

Install the pre-release editor extension from the Visual Studio Marketplace:

Terminal window
code --install-extension thinai-lang.vscode-thinai --pre-release

Install the CLI and language package from npm:

Terminal window
npm install -g thinai-cli@alpha
npm install thinai-language@alpha

The Thinai source repository is private during the alpha. See Getting started for installation details and CLI usage.

  • Identifiers are ASCII-only, including backtick-quoted names. Quoted names may contain spaces and hyphens, but not non-ASCII letters.
  • There is no direct use of another bounded context’s value object, data object, read model, or enum as a field, parameter, or return type. Use a mirror, shared kernel, integration event, or published query contract as appropriate.
  • Cross-context contribution quick fixes are intentionally unavailable because private cross-context type use is rejected. Same-context contribution quick fixes are supported.
  • The CLI validates the source file and its transitive imports, not files that import the source file. Use the language server for the full import-connected model.

The current extension focuses on core language support. It provides diagnostics, completion, definitions, find-all-references, document symbols, hover, formatting, and code actions. Rename and refactor operations are not yet available.

Same-label completion items can represent different structural path targets. Their details distinguish them; the list does not collapse them because doing so could hide a valid target.

The keyword-completion policy is spread across a few internal modules. This is maintainability debt, not a user-facing language limitation. A behavior-preserving consolidation is planned after alpha.

Use the public issue tracker and include:

  • the smallest .tni source that reproduces the issue;
  • the expected and actual result;
  • whether the issue appears in the CLI, the VS Code extension, or both;
  • your operating system and Thinai version/commit.

For language-server issues, the Thinai output channel in VS Code often contains a useful stack trace or diagnostic.