tree-sitter-objectscript 1.7.3

Objectscript grammar for tree-sitter

tree-sitter-objectscript

Tree-sitter grammars for InterSystems ObjectScript.

Grammars

This repository publishes five related grammars:

• objectscript: playground/snippet grammar.
• objectscript_udl: class-file grammar for .cls.
• objectscript_core: routine/statement grammar.
• objectscript_expr: expression grammar.
• objectscript_routine: routine-file grammar for .mac, .inc, .rtn, and .int.

Grammar extension graph: objectscript_expr -> objectscript_core -> objectscript_udl -> objectscript objectscript_expr -> objectscript_core -> objectscript_routine

Packages

• npm: tree-sitter-objectscript
• PyPI: tree-sitter-objectscript (ships tree_sitter_objectscript, tree_sitter_objectscript_udl, and tree_sitter_objectscript_routine)
• Rust crates:
  • tree-sitter-objectscript (UDL grammar)
  • tree-sitter-objectscript-routine (routine grammar)
  • tree-sitter-objectscript-playground (playground grammar)

Bindings

Language bindings are available under bindings/:

• C: bindings/c
• Go: bindings/go
• Node.js: bindings/node
• Python: bindings/python
• Rust: bindings/rust, bindings/rust-routine, and bindings/rust-playground
• Swift: bindings/swift

Quick binding checks from repo root:

nvm use
npm ci
cargo test --lib --package tree-sitter-objectscript
python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install -U pip setuptools wheel pytest tree-sitter
python3 setup.py build_ext --inplace
PYTHONPATH=$PWD/bindings/python python3 -m pytest -q bindings/python/tests/test_binding.py
npm test
go test ./bindings/go/...
swift test
make test

The routine and playground Rust crates are staged from bindings/rust-routine and bindings/rust-playground via helper scripts. See CONTRIBUTING.md for the current local build workflow and the temporary studio-highlights.scm copy step those staged crates need today.

For Node bindings specifically, .nvmrc pins the expected Node version.

Editor Integration

• Zed: ObjectScript extension
• Neovim (nvim-treesitter):
  • Install grammars with :TSInstall objectscript_udl, :TSInstall objectscript, and :TSInstall objectscript_routine
  • Optional filetype mapping for .cls and routine extensions:

vim.filetype.add({
  extension = {
    cls = "objectscript_udl",
    mac = "objectscript_routine",
    inc = "objectscript_routine",
    int = "objectscript_routine",
    rtn = "objectscript_routine",
  },
})

• Emacs: emacs-objectscript-ts-mode

Quick Development

Install the tree-sitter CLI, then run commands from a grammar directory (objectscript, udl, core, expr, or objectscript_routine):

tree-sitter generate
tree-sitter test
tree-sitter build

For playground work:

tree-sitter build --wasm
tree-sitter playground

If you change an upstream grammar (expr or core), regenerate downstream grammars as needed (udl, objectscript, objectscript_routine).

Query Sync

scripts/sync_queries.py manages the canonical query trio for each grammar:

• highlights.scm
• indents.scm
• injections.scm

It composes the layered query trees for core, udl, objectscript, and objectscript_routine, then mirrors those composed files into the Python binding query directories. studio-highlights.scm files are intentionally left out of that sync process and are maintained separately.

Corpus Sync

objectscript/test/corpus is treated as a synced corpus directory. On commit, the repository pre-commit hook:

• Replaces objectscript/test/corpus contents with files from:
  • core/test/corpus
  • udl/test/corpus
  • objectscript_routine/test/corpus
• Removes objectscript/test/corpus/invalid.txt
• Removes objectscript/test/corpus/compiled-header.txt

Contributing

See CONTRIBUTING.md for setup, workflow, query sync, and binding test instructions.

References

• InterSystems ObjectScript documentation
• Tree-sitter documentation

License

MIT. See LICENSE.