Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update {{ stage_name }}.qmd #33

Merged
merged 2 commits into from
Oct 17, 2024
Merged

Update {{ stage_name }}.qmd #33

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
173b39d
Update {{ stage_name }}.qmd
tschwarzl Oct 16, 2024
dd21a93
Update {{ stage_name }}.qmd
tschwarzl Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions src/dso/templates/stage/quarto/src/{{ stage_name }}.qmd
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,22 @@
```{r}
library(conflicted)
library(dso)
#| label: load libraries
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think label should not contain spaces as it will be a hyperlink anchor, see https://quarto.org/docs/reference/cells/cells-knitr.html#attributes

Not sure we need labels at all here?

Copy link
Contributor Author

@tschwarzl tschwarzl Oct 17, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

label can contain spaces, but yes, we can remove spaces.

labels are good practice, as it shows progress in compilation, also it can be used for referencing block dependencies (spaces are there no problem). it would be good to have show good practice in the template

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I dislike them because I forget to change them when I copy&paste a block and then compilation fails because of duplicate labels. But I agree in an ideal world one would use them.


require(conflicted)
require(dso)
```

```{r}
# Set stage dir, compile and load params
#| label: read params
# read_params sets the stage directory, runs 'dso compile-config'
# and loads params defined in the 'dvc.yaml' 'params' section of the stage

params <- read_params("{{ stage_path }}")
```

```{r}
# Obtain files relative to stage directory, e.g.
#| label: Obtain files relative to stage directory

# stage_here locates your files relative to the stage path set in read_params
# e.g.
samplesheet <- readr::read_csv(stage_here(params$samplesheet))
```
Loading