quarto-dev / quarto-dev/quarto
Source editor priorities for 2026
Open
Nobody has claimed this yet.
vscode
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
This year, we want to invest a bit in the extension here to improve the source editor experience for .qmd.
LSP features
- Diagnostics: https://github.com/quarto-dev/quarto/issues/208 (this is the top, top priority ⭐ from my perspective)
- Outline: https://github.com/quarto-dev/quarto/issues/167
Syntax highlighting (Quarto-specific, not for code cells)
Execution
- https://github.com/quarto-dev/quarto/issues/200, https://github.com/quarto-dev/quarto/issues/8 (we'll prioritize Jupyter here, but if we can also get knitr that would be great)
Editing
Publishing
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
Start by reviewing the linked issues for diagnostics, outline support, syntax highlighting, execution, editing, and publishing, beginning with issue 208 identified as the top priority. The issue does not name files or a single entry point, and completion would require choosing and implementing one or more priorities from this roadmap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100