Skip to content

Releases: NostraDavid/vscode-better-comments

v1.0.10

Choose a tag to compare

@github-actions github-actions released this 25 Oct 20:36

Changed

  • Convert tests, maintenance scripts and Webpack configuration to strict TypeScript.
  • Reuse compiler output for Node and browser bundles, removing the duplicate loader and its seven development packages.

v1.0.9

Choose a tag to compare

@github-actions github-actions released this 25 Oct 20:36

Changed

  • Replace ambient and untyped comment settings, tags and decoration ranges with explicit TypeScript contracts.
  • Narrow tag settings at the existing validation boundary while preserving all comment and language behavior.

v1.0.8

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08

Fixed

  • Respect native per-language better-comments.enabled settings and clear existing colors when disabled.
  • Refresh document settings and comment ranges when changing language in the same editor.
  • Prevent a pending read from restoring a removed language configuration in the cache.

v1.0.7

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08
  • Limit JavaScript, TypeScript, JSX and TSX decorations to real line/block comments using a small Lezer grammar shared with the existing Python parser runtime.
  • Protect URLs, strings, templates, regular expressions and JSX text without losing real trailing comments.
  • Parse once per editor update and preserve comment detection while code is incomplete.

v1.0.6

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08
  • Highlight compact and single-line block comments without coloring code after the closing delimiter.
  • Handle opening-line tags, decorative asterisks and CRLF consistently in ordinary and JSDoc blocks.
  • Apply the multiline setting to JSDoc comments as well. The boundary work follows upstream PR #457 by aarondill, adapted to preserve Python string filtering.

v1.0.5

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08
  • Use the first longest matching tag consistently in single-line, block and JSDoc comments.
  • Preserve the first configured style for case-insensitive duplicate tags. The repeated-capture correction follows upstream PR #460 by aarondill.

v1.0.4

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08
  • Apply tag, color and comment-setting changes immediately in every visible editor.
  • Keep parser state per editor and discard stale asynchronous updates.
  • Dispose obsolete decoration types and pending updates when editors or the extension close.
  • Refresh language definitions without retaining removed extension configurations.

v1.0.3

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08
  • Highlight genuine comments on the first line of Python, Elixir and Tcl files.
  • Skip only a file-leading shebang, including shell scripts; retain later comment markers and CRLF support.

v1.0.2

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:08
  • Validate tag settings without crashing activation; keep valid tags active when other entries are malformed.
  • Keep empty tags supported and use the first configured style for case-insensitive duplicates.
  • Describe tag fields in the settings schema, following upstream PR #400 by Take-Me1010.

v1.0.1

Choose a tag to compare

@NostraDavid NostraDavid released this 25 Oct 18:07
  • Keep assigned Python triple-quoted strings unstyled across every comment detector.
  • Reset language-specific detection when switching editors, preventing JavaScript JSDoc highlighting from leaking into Python.
  • Exercise all comment detectors with Python block-marker configuration in regression tests.