Unknown language in `contributes.grammars.language` warning for `chef_berkshelf`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 18
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 3
Description
Description
When activating the Chef Infra extension in VS Code, the following warning is raised:
Unknown language in contributes.grammars.language. Provided value: chef_berkshelf
This happens because chef_berkshelf is referenced in the grammars contribution point of package.json, but is never declared as a language in the languages contribution point. VS Code requires every language ID referenced in grammars to have a corresponding entry in languages.
Steps to reproduce
- Install the Chef Infra extension v2.2.12 in VS Code
- Open any Chef repository
- Observe the warning in the VS Code developer console (Help → Toggle Developer Tools → Console)
Expected behavior
No warning should be raised. Either chef_berkshelf should be declared as a language in the languages contribution point, or the grammar entry referencing it should be removed if Berkshelf support is no longer intended.
Actual behavior
The following warning appears on every extension activation:
Unknown language in contributes.grammars.language. Provided value: chef_berkshelf
Environment
VS Code version: 1.116.0
Extension version: 2.2.12
OS: Windows 11
Docker Desktop: 4.69.0
Container image: chef/chefworkstation:stable
Additional context
The issue was found while using the extension inside a Dev Container based on chef/chefworkstation:stable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in package.json by comparing the chef_berkshelf entry under contributes.grammars with the extension's contributes.languages entries. Confirm whether Berkshelf support is intended, then make the contribution points consistent. Install or activate the extension in VS Code and check the developer console to verify that the warning no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100