quarto-dev / quarto-dev/quarto
Feature request: Extensibility of the standalone Quarto visual editor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
It's been great to experiment with RStudio's transition to Electron. Will the forthcoming standalone Quarto visual editor also be based on Electron?
If so, given the runaway success of extension registries for Electron-based text editors (e.g. Obsidian, VS Code, OpenVSX), do you anticipate making an extension API (e.g., Obsidian API, VS Code API) available for the standalone Quarto visual editor?
A final thought is, given the polyglot spirit of Quarto, would such an API have bindings to JavaScript/TypeScript only, or could it have bindings to R and Python?
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
The issue names no files, tests, or entry points. Start by locating the standalone Quarto visual editor and its Electron/TypeScript architecture, then determine the scope of an extension API and possible R and Python bindings. Done means an agreed API design and an implemented, documented extension path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100