quarto-dev / quarto-dev/quarto-cli

using `resources:` field in `_quarto.yml`

Open
#3,766 7 comments 1 reaction 1 assignee View on GitHub

@cscheid is already working on this.

Since Dec 27, 2022.

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

Description

Discussed in https://github.com/quarto-dev/quarto-cli/discussions/3763

Originally posted by ijlyttle December 26, 2022
I am working on a PR for pins (rstudio/pins-r#692), and have gotten myself confused about how to use resources: in _quarto.yml. I don't know if I have found a bug, or if I am just doing it wrong. Hopefully someone can point me in the right direction.

I see this is discussed also in https://github.com/quarto-dev/quarto-cli/discussions/3443.

Here's my _quarto.yml file:

project:
  type: website
  resources:
    - data/board_one

resources:
  - data/board_two

board_one and board_two are directories; my goal is that they be copied recursively into _site/.

I find this works for board_two, even though this resources: isn't in the documented location.

However, for board_one, it copies the file in the folder, but not the folder inside. I get these warnings when I render locally:

WARNING: File 'data/board_one/mtcars/20221226T175420Z-c2702' was not found.
WARNING: File 'data/board_one/mtcars/20221226T175420Z-c2702/data.txt' was not found.
WARNING: File 'data/board_one/mtcars/20221226T175420Z-c2702/mtcars.json' was not found.

I have a (hopefully) reproducible repo, rendered and published with an action; here's the data directory.

I am using quarto 1.3.56.

Thanks!

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.