← All extensions

InterSystems ObjectScript

v1.4.0 · by Dave McCaldon, Hannah Kimura · added 3 November 2026

InterSystems IRIS ObjectScript Extension

Languages

How to install

With Forge Super installed, the button above opens the app on this extension, where you press Install. Nothing is installed until you do.

You can also open the Extensions panel in the app and search for InterSystems ObjectScript. The extension's id is objectscript.

Don't have Forge Super yet? Download it here.

README

From the extension's repository, written by its authors and not by Mentenaz. See the source.

Zed ObjectScript

An ObjectScript extension for Zed to support development for the InterSystems IRIS product.

![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-%23FE5196?logo=conventionalcommits6logoColor=white)

Introduction

This Zed extension uses the tree-sitter-objectscript grammar to provide syntax highlighting and code injections for .cls files containing ObjectScript. Since ObjectScripts supports a number of embedded languages, you should install grammars for the following languages otherwise you may see areas that appear to lack syntax coloring.

  • SQL
  • HTML
  • Python
  • JavaScript
  • CSS
  • XML
  • Markdown

NOTE: The ObjectScript .cls syntax supports some sophisticated constructs and as such it can take 15-60 seconds for Zed's WASM machinery to build the parser before syntax coloring becomes available.

Currently this extension only provides syntax coloring support.

Reporting Issues

Please report issues via GitHub Issues.

Contributing

Contributions are welcome. Please submit changes via Pull Requests. Our preference is to use Conventional Commits for commit messages in order to keep the summaries terse, but allowing for more detail on the subsequent lines of the commit message.

Development

To develop this extension, see the Developing Extensions section of the Zed docs.

Notes

To enable log output for Zed, set RUST_LOG as follows before starting zed from the command line:

$env:RUST_LOG = "language,extension=trace"
RUST_LOG = "language,extension=trace"

Cloning and the building a debug Zed with these RUST_LOG settings gives fairly detailed log output including diagnosing bad .scm rules.