Epic: Execution Planner

Open
#6,518 1 comment 21 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Aug 14, 2023.

Assessment

This issue has not been assessed yet.

Description

epic files

In our TypeScript codebase, we need a source of truth for which input files produce which output files (and which temporaries).

Potential wins once we have this:

  • parallelization
  • change output locations (including slugs, etc)
  • safer parameterized reports
  • avoid file overwriting

Issues:

  • #6472
  • #10841
  • #6116
  • #5861
  • #4730
  • #4802
  • #690
  • #906
  • #1152
  • #1294
  • #1666
  • #2065
  • #2216
  • #2375
  • #2363
  • #6809
  • #6045
  • #4583
  • #6392
  • #8367
  • #8373

Notes

Lockfiles

When fixing #6472, we should consider a design for lockfiles, so that different instances of running quarto (which happens often when running a VS code preview and a command-line render, like in our test suite) don't step on each other's toes.

  • #8626 (.quarto should be versioned)

  • #4632

Other things to do

  • when doing notebook embedding, we currently do a lot of this kind of "file exists" reasoning. That should be a part of this planner instead.
  • this is also involved in getting multiple versions of a same page to be rendered (dark + light, mobile + desktop, etc)
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.