redhat-developer / redhat-developer/vscode-yaml
`.clang-format` have schema, extension complain `No JSON Schema`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
.clang-format have schema, extension complain No JSON Schema
Expected Behavior
.clang-format have schema, extension should detect it
Current Behavior
.clang-format have schema, extension complain No JSON Schema
Steps to Reproduce
/path/to/c/.clang-format
BasedOnStyle: LLVM
YAML UI No JSON Schema when
{
"folders": [
{
"name": "c",
"path": "/path/to/c",
},
],
"settings": {
"yaml.schemas": {
// "https://json.schemastore.org/clang-format.json": ".clang-format"
},
},
}
YAML UI .clang-format config when using below workaround
{
"folders": [
{
"name": "c",
"path": "/path/to/c",
},
],
"settings": {
"yaml.schemas": {
"https://json.schemastore.org/clang-format.json": ".clang-format"
},
},
}
But this config should be default within schema store.
{
"name": "clang-format (.clang-format)",
"description": "yaml clang-format config",
"fileMatch": [".clang-format"],
"url": "https://json.schemastore.org/clang-format.json"
},
So, there also might be other config file, with schema, but not silently not enchanced by yaml extension.
Environment
- Windows
- Mac
- Linux
- other (please specify)
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
Reproduce the issue with a .clang-format file containing BasedOnStyle: LLVM, first without and then with the yaml.schemas workaround. Inspect the SchemaStore catalog.json clang-format entry and the extension's schema-discovery entry points to determine why its fileMatch is missed. Done means .clang-format receives the clang-format schema without manual configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode, yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100