Releases: lightning-js/blits-dev-tools
Releases · lightning-js/blits-dev-tools
blits-vscode v1.5.1
- Fixes template detection issues caused by AST-based detection methods.
- Fixes extension activation issues caused by opening a parent folder of a Blits project. Now nested project folders are supported if they have a Blits dependency in their
package.json
- Fixes bugs related to
.blits
file type implementation. - Adds integration tests
- Removes the info notification displayed when the extension is activated. Now the extension name and version are displayed in the bottom right of the editor
- Adds a check to see if the project uses
prettier-plugin-blits
(will be available soon). If so, the extension leaves template formatting to the prettier plugin.
blits-vscode v1.5.0
- Fixes a crash issue during template parsing when the AST was invalid
- Fixes module resolution issues for
.blits
files, including support for import aliases and standard libraries - Adds support for Blits v2-style props, now integrated into IntelliSense suggestions PR #364
blits-vscode v1.4.0
- Fixed syntax highlighting issue for
@updated
event attribute - Auto file template provider for newly created .blits files
- Snippet support for JavaScript/TypeScript/Blits files
- Reduced the final extension size
blits-vscode v1.3.0
- Template attributes are suggested based on the context and their parent tags
- Attribute suggestions provide information about each attribute/prop in an info window
- Attribute data is retrieved from the Blits repository with a local fallback option
- Component attributes override built-in attributes when they share the same name
- Selecting an attribute from suggestions automatically inserts its default value
- Event attributes (
@loaded
and@error
) are syntax highlighted for both.blits
and JavaScript/TypeScript files, and their expected value format is validated - The extension features for JavaScript & TypeScript files are only enabled when the workspace contains a
package.json
file with@lightningjs/blits
dependency..blits
file features are always active - If a template has major structural errors that prevent auto formatting, the editor now underlines the entire template in red (as an error) and displays an error message when hovering over the template
- Fixed the issue where interpolated attribute names with hyphen are not highlighted correctly (fixes #27)
- Template handling has been improved.
template
properties of objects outsideBlits.Component()
calls are considered Blits templates only when they match a Blits template string format. Otherwise, they are treated as regular text, and extension features are disabled for those strings. This fixes false positive cases while parsing potential Blits template strings in JavaScript and TypeScript code. - Syntax highlighting rules/patterns are improved for template strings in JavaScript/TypeScript files
- Fixed bugs related to auto formatting when single quotes are used for defining template strings
- Fixed the issue of displaying forward slashes in red for some self-closing tags (like
<Button />
) by improving syntax grammar rules - Fixed code completion implementation. Suggestions for template tags and attributes are now only offered in appropriate contexts. Characters that trigger suggestions are strictly controlled. Removed duplicate items that appeared when users requested only the list of regular attributes
- Fixed bugs related to template strings that begin with HTML-style comments
- Fixed syntax highlighting for regular attribute values by ensuring proper quote matching in grammar regex in
.blits
files.
blits-vscode v1.2.1
- Fixes the commenting issue in TypeScript files caused by an incompatible babel parser plugin
blits-vscode v1.2.0
- Fixes an auto-formatting issue where the extension removes trailing spaces unexpectedly.
- Resolves an auto-formatting issue where extra indentation is applied to multiline attribute values on every file save.
- Addresses formatting issues for
.blits
files: template and script sections are now formatted independently. The script section respects to user-defined formatting rules configured in VS Code for the extension. - Implements IntelliSense suggestions for template tags, supporting both built-in and custom components. (fixes #16 )
blits-vscode v1.1.0
- Fixes the error displayed when a
.blits
file is imported into TS/JS files. - Fixes commenting bugs in TS/JS files.
- Removes block-level commenting; each line is now commented out separately within template strings (TS/JS components).
- Fixes a bug that removed all empty lines in template strings.
- Fixes the json file import issue in
.blits
files. - Fixes the extra line added after template strings by removing whitespace following the last template tag.
- Fixes AST parsing issues and adds additional Babel plugins.
blits-vscode v1.0.0
- Implemented the new
.blits
file type with its own TextMate grammar file. - Integrated existing functionality into the
.blits
file format. - Fixed syntax highlighting issues for deprecated HTML tags and attributes. (fixes #21 )
- Added improved IntelliSense support for template attributes by parsing renderer props from the Blits codebase.
- Implemented caching for parsing renderer props to prevent performance issues.
- Included minor bug fixes and code refactoring.
- Implemented a syntax highlighting grammar file for Blits code embedded in Markdown files.
- Implemented an error-checking feature that displays a warning if a for-loop index is used in the
key
attribute. - Implemented JavaScript & TypeScript editor features for embedded JavaScript / TypeScript content inside
.blits
files. - Merged project
tsconfig.json
andjsconfig.json
with extension defaults to maintain critical settings while allowing user customizations (regarding.blits
file editor features). - Resolved an issue where commenting multiple lines out in the template strings (in
.js
/.ts
files) caused their indentation to increase with each save.
blits-vscode v0.5.0
Version 0.5.0 of lightning-blits
blits-vscode v0.4.1
Version 0.4.1 of lightning-blits