Extension issue
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 18
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 3
Description
- Issue Type:
Bug - Extension Name:
chef - Extension Version:
2.1.0 - OS Version:
Windows_NT x64 10.0.14393 - VS Code version:
1.58.2
⚠️ We have written the needed data into your clipboard. Please paste! ⚠️
{
"messages": [
{
"type": 3,
"message": "Unknown language in `contributes.grammars.language`. Provided value: chef_berkshelf",
"extensionId": {
"value": "chef-software.chef",
"_lower": "chef-software.chef"
},
"extensionPointId": "grammars"
}
],
"activationTimes": {
"codeLoadingTime": 26,
"activateCallTime": 0,
"activateResolvedTime": 48,
"activationReason": {
"startup": true,
"extensionId": {
"value": "chef-software.chef",
"_lower": "chef-software.chef"
},
"activationEvent": "workspaceContains:**/metadata.rb"
}
},
"runtimeErrors": []
}
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 by locating the Chef extension's grammar contribution for the chef_berkshelf language and reproduce the warning in VS Code. The issue provides no file or test location; done should mean the reported unknown-language warning is resolved without introducing runtime errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100