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

chore: change LSP and VSCode extension diagnostics #13

Merged
merged 8 commits into from
Aug 18, 2023

Conversation

ematipico
Copy link
Member

@ematipico ematipico commented Aug 18, 2023

Summary

Notable changes:

  • changed the LSP internals by replacing rome with biome;
  • changed version to 0.1.0 to trigger to CI;
  • updated the dependencies of the VSCode extension;
  • updated the codegen of the linter;

Test Plan

Merge and try to publish the extension

@ematipico ematipico temporarily deployed to Website deployment August 18, 2023 08:45 — with GitHub Actions Inactive
@github-actions github-actions bot added A-CLI Area: CLI A-Linter Area: linter A-Tooling Area: internal tools A-LSP Area: language server protocol A-Website Area: website labels Aug 18, 2023
@ematipico ematipico temporarily deployed to Website deployment August 18, 2023 08:49 — with GitHub Actions Inactive
@ematipico ematipico temporarily deployed to Website deployment August 18, 2023 08:52 — with GitHub Actions Inactive
@ematipico ematipico temporarily deployed to Website deployment August 18, 2023 08:57 — with GitHub Actions Inactive
@ematipico ematipico temporarily deployed to Website deployment August 18, 2023 09:04 — with GitHub Actions Inactive
@ematipico ematipico temporarily deployed to Website deployment August 18, 2023 10:28 — with GitHub Actions Inactive
@ematipico ematipico merged commit 0edaece into main Aug 18, 2023
18 checks passed
@ematipico ematipico deleted the chore/more-changes branch August 18, 2023 10:41

[Rome](https://biome.tools/) unifies your development stack by combining the functionality of separate tools. It uses a single configuration file, has fantastic performance, and works with any stack. This extension brings Rome to your editor so that you can:
[Biome](https://biome.tools/) unifies your development stack by combining the functionality of separate tools. It uses a single configuration file, has fantastic performance, and works with any stack. This extension brings Biome to your editor so that you can:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

biomejs.dev?

@@ -6,17 +6,17 @@ description: Notes about the Biome's VSCode extension
---
# Biome VS Code Extension

[Biome](https://biomejs.dev/) unifies your development stack by combining the functionality of separate tools. It uses a single configuration file, has fantastic performance, and works with any stack. This extension brings Biome to your editor so that you can:
[Biome](https://biome.tools/) unifies your development stack by combining the functionality of separate tools. It uses a single configuration file, has fantastic performance, and works with any stack. This extension brings Biome to your editor so that you can:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

biomejs.dev?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CLI Area: CLI A-Linter Area: linter A-LSP Area: language server protocol A-Tooling Area: internal tools A-Website Area: website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants