Skip to content

Releases: ktav-lang/editor

v0.6.1

Choose a tag to compare

@github-actions github-actions released this 05 Jun 14:26
  • Docs: rewrite all README examples to spec 0.6 syntax (bare numbers instead of removed :i/:f markers; ## comments instead of #).
  • LSP: remove :i/:f from completion items (typed markers removed in spec 0.5).

Ktav editor support 0.6.0 — VS Code + JetBrains + LSP

Choose a tag to compare

@github-actions github-actions released this 01 Jun 21:31

Tracks ktav Rust crate 0.6.0 and ktav-lang/spec 0.6.0. The
version is realigned to move in lockstep with the format/core (the
previous editor release was 0.3.1). The spec change is key
escaping
: keys now process the § 3.7 escape set and add \. (a
literal dot that does not split a dotted path) and \: (a literal
colon that is not a pair separator); a literal backslash in a key is
now written \\. Editor support is updated end-to-end so highlighting,
tokens and diagnostics treat escaped key bytes correctly.

LSP server (ktav-lsp)

  • Semantic tokens, document symbols and diagnostics are now
    escape-aware: the pair separator is the first unescaped : / ::
    and dotted-path splitting happens only on unescaped .. So
    a\.b: v is the single key a.b, and a\:: v is the key a: with
    value v.
  • Depends on ktav 0.6.0.

IntelliJ plugin

  • KtavLexer lexes escaped key segments (\\ \. \: \, \} \] \{ \[ \n \r),
    so a key containing an escaped dot or colon highlights as one key.

TextMate grammar (VS Code + shared grammars/)

  • The key-segment pattern accepts \-escapes, matching the spec's key
    escape set.

Ktav IntelliJ plugin 0.5.1

Choose a tag to compare

@PHPCraftdream PHPCraftdream released this 31 May 12:22

IntelliJ Platform plugin 0.5.1 — Marketplace compatibility fix + full verifier cleanup.

Changes

  • Compatibility range raised to IntelliJ 2023.1+ (since-build 231) — resolves the hard incompatibility on 2022.x (ProjectActivity exists only from 2023.1). Every build 231+ verifies as Compatible.
  • Removed all deprecated / internal platform-API usages flagged by the JetBrains Plugin Verifier (no behaviour change):
    • CodeInsightColors.INFO_ATTRIBUTESWEAK_WARNING_ATTRIBUTES
    • TextFieldWithBrowseButton.addBrowseFolderListener(title, …) → manual FileChooser.chooseFile
    • TextAttributesKey.createTextAttributesKey(String, TextAttributes)enforcedTextAttributes
    • FileChooserDescriptorFactory.createSingleFileDescriptor() → the FileChooserDescriptor constructor
    • Document.addDocumentListener(listener) → the Disposable overload (also fixes a listener leak)
    • DaemonCodeAnalyzer.restart() → per-open-file restart(PsiFile)
    • internal PluginManagerCore.getPlugin(id) → the plugin's own class-loader descriptor
    • Verifies warning-free on 2023.1 → 2024.3 (the buildable SDK); the same replacements target the newer-SDK warnings on 2025.1+/2026.x.
  • Bundles the same ktav-lsp 0.5.0.

Artifact

ktav-intellij-0.5.1+20260531-1420.zip — universal build (~10.5 MB), all 6 platform LSP binaries, loads on every JetBrains IDE (2023.1+) on every OS.

Scoped IntelliJ-plugin release; the ktav-lsp crate and the VS Code extension remain at 0.5.0.

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 29 May 17:48
editor 0.5.0 — spec/ktav 0.5.0 sync, highlighting parity, icon, build…