Automatic Comment Blocks v1.1.11

Fixes #13 by normalizing the onEnter properties to use the API format

Full Changelog: v1.1.10...v1.1.11

Automatic Comment Blocks v1.1.10

What's Changed

• Fix the extension failing to get language configs from extensions (built-in and user) when running in WSL2, in PR #12 which fixes #6 and indirectly #7, among other bug fixes, general maintenance and improvements.

---

Bug Fixes and Enhancements:

• WSL Compatibility Fixes: Resolved issues where the extension failed to detect built-in extensions on Windows when running in WSL by merging Windows and WSL-installed extensions.
• Improved Language Support: Fixed detection of disabled languages, improved merging of multiple configuration files, and handled comment configurations more effectively.

New Features:

• macOS Keybinding Support: Added cmd+shift+m keybinding for Blade override comments on macOS.
• New Dependencies: Added is-wsl for WSL detection and package-json-type for TypeScript type definitions of package.json objects.

Codebase Refactoring:

• ExtensionData Class: Introduced a new ExtensionData class for centralized management of extension metadata, improving maintainability and debugging.
• Utility Functions: Extracted common functionality into a new utils.ts file for better code reuse.

---

Full Changelog: v1.1.9...v1.1.10

Automatic Comment Blocks v1.1.9

What's Changed

• Fix single-line comment config changes in VS Code June 2025 release; in PR #11 which fixes #10.

Full Changelog: v1.1.8...v1.1.9

Automatic Comment Blocks v1.1.8

A patch to:

• Fix the debug logger not logging regex meta data in the language config files as found in the log files in #6.

• Add the logging of:

  • The extension's user config settings.
  • Various VS Code environment info.
  • Various System environment info.

  This allows for a more complete debugging diagnostic report.

Full Changelog: v1.1.7...v1.1.8

Automatic Comment Blocks v1.1.7

A patch to add the ability to log debug information to a dedicated Auto Comment Blocks channel in the Output panel. This is to help diagnose issues quicker.

Full Changelog: v1.1.6...v1.1.7

Automatic Comment Blocks v1.1.6

A patch to add the ability for the extension to automatically create the auto-generated-language-definitions directory if it doesn't exist, because the those files will no longer be packaged into the .vsix file since they're auto-generated anyway.

Full Changelog: v1.1.5...v1.1.6

Automatic Comment Blocks v1.1.5

A patch to fix #4

Full Changelog: v1.1.4...v1.1.5

Automatic Comment Blocks v1.1.4

Fixed:

• When singleLineBlockOnEnter setting is true, and when then cursor is in the middle of the text, eg. // text | text, the comment would not be continued on the next line when enter is pressed. Therefore the text after the cursor would not be a comment on the new line.

• The known issue: if you enable the singleLineBlockOnEnter setting, for some languages, including C, C++, Sass - pressing tab immediately after breaking out of a comment block, will insert a commented line.

  This seems to only happen in languages without indentationRules, so it's fixed by adding default indentation rules with empty strings.

  Note: Using empty strings shouldn't have any side effects, but please report an issue if you have any problems with indentation.

For a Full Changelog please view the commits: v1.1.3...v1.1.4

Automatic Comment Blocks v1.1.3

Fixed single-line comments onEnter not working when indented.

Full Changelog: v1.1.2...v1.1.3

Automatic Comment Blocks v1.1.2

Fixed single-line comments were not inserting new commented lines for any languages when pressing enter (when singleLineBlockOnEnter was set to true), caused by an unknown bug within VScode itself.

Also, in JavaScript and TypeScript files, pressing tab on an empty line may insert a * on that line. Probably the same bug as above. The regex fix inadvertently fixes #2

Note: v1.1.1 of the extension was released on the marketplace by mistake without a changelog. The official bug fix is v1.1.2.

Full Changelog: v1.1.0...v1.1.2