quarto-dev / quarto-dev/quarto
Support for VS Code Virtual Environments?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
VS Code offers an option to remotely browse and edit a GitHub repository. For instance, if you open a repository with the VS Code for Web (github.dev) you can use the "Continue Working On..." option to open the repo locally without the need of cloning. This is very convenient for editing and reviewing PRs, for instance, because you can use the Quarto Visual Mode (which is not available in the web version).
Quarto extension mostly works in this mode, except for the render option that does nothing. I guess this is because the extension does not have support for virtual environments. Not use about the impact of this and how limited the support would be, but it could be nice to have.
Thanks for the great work!
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 with the Quarto extension's render option in a VS Code virtual workspace opened through Continue Working On..., and compare its behavior with a locally cloned repository. Done means the render action works in the described virtual-workspace flow, with the supported limitations clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100