You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
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 outside Blits.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.