The .vsix i can download from the marketplace throws this error when instlaling in code-server:
Corrupt ZIP: end of central directory record signature not found
I could somehow solve this problem by packaging the extension myself after cloning this repo.

Any thoughts on removing the yaml file and the build step all together?

I want to navigate the component file automatically on click the Component definition itself. More like javascript when you mouseover on any code and if you click the code it opens that component file.

What do we need to enable CSS highlighting & autocomplete in syntax highlighting? Can we somehow pipe Emmet in?

Hello!

I noticed inline comments support was added after version 0.5.0 and I can't see a version bump since then. Is there a way to manually install the latest version of the extension into VS Code, or do we need to wait for a version bump? I don't have any experience with VS Code extensions, but if a version bump is required and fairly simple, I'm happy to give it a go and submit a PR.

Thanks!

Would be nice to have mint.json keys autocomplete. Any general thoughts or insights regarding best practices?

The vsce tool timeout when trying to publish the latest version.
The issue is related to microsoft/vscode-vsce#446

mint-lang/mint-website-rails#40

I don't know if mint has any kind of formal debugger functionality at the moment, but in the absence of that, perhaps we can launch/restart/kill the development server using the F5 debugger tools? Thoughts?

What do we need to enable Option+Shift+F file formatting support?

It looks like mint format doesn't have any arguments for a specific file which is not ideal for this feature, but triggering a global format would be better than nothing. Also format on save.

It seems to me that we should add the following commands to the VSCode command palette at a minimum. Thoughts?

• mint build
• mint init
• mint install

The VS Code docs state:

Highlighting based on semantic tokens is considered an addition to the TextMate-based syntax highlighting. Semantic highlighting goes on top of the syntax highlighting. And as language servers can take a while to load and analyze a project, semantic token highlighting may appear after a short delay.

To be honest, I would not mind the tiny delay, Since our language server is built in Crystal, it's fast, and it should not be a problem if we skip the tmLanguage definition.
The benefits would be correct highlighting, better maintainability.

For Reference:

• microsoft/vscode#86415
• https://github.com/microsoft/vscode/wiki/Semantic-Highlighting-Overview
  The links on the bottom of the wiki page point to the API which is necessary.
  It's also important to point out that this Semantic Tokens Spec is not specific to VS Code, It will be part of the next LSP version 3.16.0, so other editors will begin to adopt it.
• https://github.com/microsoft/vscode-extension-samples/tree/master/semantic-tokens-sample

Copied from conversation at Mint Lobby