quarto-dev / quarto-dev/quarto
Use `ExecuteQueue` for all `execute()` hooks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Follow up to https://github.com/quarto-dev/quarto/pull/510
In #510 we added ExecuteQueue and use it for cell execution in Positron to ensure that R and Python cells are sent to Positron for execution in the correct order.
https://github.com/quarto-dev/quarto/issues/509#issuecomment-2332435708 revealed that we really need to do this anywhere we are using execute(), since it shows it is broken in VS Code with R too, so we should go through and fix those other cases too.
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 PR #510, then locate every use of execute() and compare those paths with the ExecuteQueue integration used for Positron cell execution. Check the VS Code and R execution paths described in issue #509; done means all execute() hooks use the queue and preserve correct execution order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100