Skip to content

Epic: Execution Planner #6518

@cscheid

Description

@cscheid

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:

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.

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)

Sub-issues

Metadata

Metadata

Assignees

Labels

epicAn issue that contains other issuesfilesIssues related to temporary file locations, nonstandard output locations, etc

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions