quarto-dev / quarto-dev/quarto-cli
Could we communicate resource directory information post rendering for external tooling ?
Open
Nobody has claimed this yet.
enhancement
inspect
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
I don't know if this is known in advance. It probably should, and then made available through inspect
Use case: cleaning after a rendering when calling quarto render for tests.
Currently this can be done by convention (looking for <input>_files folder)
Contributor guide
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 tracing the quarto render and inspect entry points to see whether the resource directory is known during rendering and how post-render information is exposed. Define the external-facing result needed for cleanup tooling, then verify that a test render can obtain the resource directory without relying on the _files naming convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100