JaggerScript / docsProject documentation

Reference

Diagnostics and Editor Tooling

Look up syntax, contracts, layouts, algorithms, and exact behavior.

The browser integration wraps the parser with Monaco diagnostics. Parse failures are converted into editor markers with line and column ranges. A lightweight semantic pass also identifies unknown declared types by comparing declarations against primitive type names and class names found in the current source.

m=(lines,cols,linee,cole,message,severity)m = (line_s, col_s, line_e, col_e, message, severity)
Marker mapping. Parser locations are converted into Monaco marker records so syntax errors attach to source spans.

Syntax highlighting is supplied through a Monarch tokenizer. Keywords, type keywords, function names, console calls, identifiers, class names, strings, numbers, comments, delimiters, and operators receive separate token classes. The editor route therefore presents the language as an owned tool rather than plain text in a generic textarea.

  • The Check action parses and reports diagnostics without running the program.
  • The Run action captures console output and restores the original console hooks after execution.
  • Examples are imported as raw source files so the playground and repository tests share the same corpus.
  • Editor theme state is persisted locally and does not affect runtime behavior.

Continue exploring

Tutorials →How-to guides →Explanation →Source repository →