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

Automatic Comment Blocks v1.1.0

What's Changed

Added automatic-language support.
Removed handcoded language definitions.

• Release v1.1.0 by @yCodeTech in #1

Fixes:

• kevb34ns#44
• kevb34ns#41
• kevb34ns#40
• kevb34ns#28
• kevb34ns#27
• kevb34ns#24
• kevb34ns#12

Fixes but dependant on 3rd party language extensions are installed or defined in the user settings:

• kevb34ns#38
• kevb34ns#26
• kevb34ns#17
• kevb34ns#13
• kevb34ns#11

For more information, on auto-support please read the README file.

Full Changelog: v1.0.3...v1.1.0

v1.0.3

Automatic Comment Blocks v1.0.3

Note: Released on VS Code Marketplace on 17/09/2022; started GitHub releases on 17/11/2024.

Notable changes

• Added support for JavaScript and TypeScript multiline block comments - a pull request by a-stewart for the original plugin. Fixes issue kevb34ns#27.
• Created a new language config file for Blade to use blade's comments as well as the multiline block comments
• Updated various language config files to reflect a pull request by a-stewart for the original plugin.
• Added support for protocol buffers - a pull request by jun-sheaf for the original plugin.
• Added support for //! comments - a pull request by Lucretiel for the original plugin and fixes the issue kevb34ns#25
• Added support for csharp(c#) (using the cpp(c++) config file) - Fixes the issue kevb34ns#41.
• Updated the support for /*! */ comments and including the ! on every line.

Full Changelog: https://github.com/yCodeTech/auto-comment-blocks/commits/v1.0.3