Skip to content

Conversation

@remcohaszing
Copy link
Contributor

Summary

Rename the gritql language ID to grit

Description

The official Grit extension registers the grit language ID. The Biome extension only recently registered the gritql language ID for the same file pattern. This is a conflict. For consistency within the VSCode ecosystem, it’s best to stick with one common language ID.

Related Issue

N/A

Checklist

  • I have tested my changes on the following platforms:
    • Windows
    • Linux
    • macOS

The official Grit extension registers the `grit` language ID. The Biome
extension only recently registered the `gritql` language ID for the same
file pattern. This is a conflict. For consistency within the VSCode
ecosystem, it’s best to stick with one common language ID.
@remcohaszing remcohaszing requested review from a team and nhedger as code owners November 14, 2025 10:35
Copy link
Member

@ematipico ematipico left a comment

Choose a reason for hiding this comment

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

Instead of renaming, can you add it? There's a chance that this change will break the Biome language server unless we update core too (it will still break past versions of Biome language server)

@remcohaszing
Copy link
Contributor Author

Could you elaborate? A text document only has one language ID.

@remcohaszing
Copy link
Contributor Author

I’m not familiar with Rust or the Biome code base, so please correct me if I’m wrong. But from this line, it looks like the Biome language server even expects the grit language ID. https://github.com/biomejs/biome/blob/041196bc2a1d62f2cde758884e85d180491ff2da/crates/biome_grit_syntax/src/file_source.rs#L44

I think it only worked with the gritql files because of the file extension.

@ematipico
Copy link
Member

Yeah you're right, you can discard my previous comment:)

@nhedger nhedger merged commit f1cb534 into biomejs:main Nov 15, 2025
2 checks passed
@remcohaszing remcohaszing deleted the grit-language-id branch November 15, 2025 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants