quarto-dev / quarto-dev/quarto-cli

`quarto inspect` and temporary directories

Open
#906 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement inspect
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

From https://github.com/rstudio/rstudio/pull/11201#issuecomment-1128685959

With this R code:

dir.create(tf <- tempfile()); 
dir.create(file.path(tf, "sub"))

main <- file.path(tf, "main.qmd")
writeLines("---\ntitle: quarto document\n---\n", main)

sub <- file.path(tf, "sub", "sub.qmd")
writeLines("---\ntitle: quarto document\n---\n", sub)

writeLines('project:\n  title: "test"\n', file.path(tf, "_quarto.yml"))

system(paste0("quarto inspect ", tf, "/main.qmd | grep project"))  
system(paste0("quarto inspect ", tf, "/sub/sub.qmd | grep project"))  

getting:

> system(paste0("quarto inspect ", tf, "/main.qmd | grep project"))  
  "project": "../../../private/tmp/RtmpAMjixD/file1842c7157d908"
> system(paste0("quarto inspect ", tf, "/sub/sub.qmd | grep project"))  
  "project": "../../../../private/tmp/RtmpAMjixD/file1842c7157d908"

In https://github.com/rstudio/rstudio/pull/11201#issuecomment-1128685959 I worked around it by by using workingDir but I was wondering if this was an issue.

% quarto --version
0.9.415

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.

Research direction

Start by running the supplied R reproduction with quarto inspect on both main.qmd and sub/sub.qmd, using the reported Quarto version as a baseline. Trace how the CLI resolves the temporary project directory and verify that both invocations report a consistent project location rather than depth-dependent paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, r
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.