quarto-dev / quarto-dev/quarto
Quarto extension pollutes Extension Host output channel with a lot of warnings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
In VS Code, the Quarto extension generates quite a lot of warnings that I believe are extraneous in the "Extension Host" output channel:
For searchability, here is an example:
[warning] [quarto.quarto] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[markdown]', provide the URI of a resource or 'null' for any resource.
Contributor guide
No contributing guide indexed for this repository
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 warning in VS Code while using the Quarto extension, then trace the configuration access that emits it. Confirm that the Extension Host output no longer contains extraneous warnings while Quarto continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100