Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Zap LSP #11

Open
sasial-dev opened this issue Dec 17, 2023 · 2 comments
Open

[FEAT] Zap LSP #11

sasial-dev opened this issue Dec 17, 2023 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@sasial-dev
Copy link
Collaborator

sasial-dev commented Dec 17, 2023

Zap should have an LSP with a companion VSCode extension. This opens the door for other editor's support down the line.

@sasial-dev sasial-dev added the enhancement New feature or request label Dec 17, 2023
@jackdotink
Copy link
Member

Adding as a summary of discord discussion:

While VSCode may use monaco, it requires textmate grammar files be used for syntax highlighting. We could move to attempt using textmate grammar in docs, or maintain two different highlighters.

My own personal thoughts:

I think we should wait some time for the zap grammar to stabilize, and then create a full LSP and formatter - a formatter especially.

@jackdotink
Copy link
Member

I think this is an issue that should now be prioritized. We're getting a lot more usage of Zap, and the current workflow is quite poor. To get basic syntax highlighting you have to use the playground, which isn't ideal.

We should create a textmate grammar for Zap, use that for a vscode extension and for the docs website.

@sasial-dev sasial-dev changed the title [FEAT] VSCode Extension [FEAT] Zap LSP Mar 23, 2024
@sasial-dev sasial-dev added this to the 0.7 Release milestone Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants