Skip to content

Commit 61e1b61

Browse files
Merge pull request #52 from miraisolutions/feature/26-revise-target-blank
Revise default target blank
2 parents 5c9a13a + ec79d3f commit 61e1b61

7 files changed

+49
-55
lines changed

index.Rmd

+3-6
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,8 @@ site: bookdown::bookdown_site
88
output:
99
bookdown::gitbook:
1010
css: styles.css
11-
includes:
12-
in_header: target-blank.html
13-
pandoc_args: ["--number-offset=0"]
14-
# disable alt text rendered as figure caption
1511
split_by: section
12+
# disable alt text rendered as figure caption
1613
fig_caption: false
1714
config:
1815
sharing:
@@ -31,7 +28,7 @@ mod_date_envir <- list2env(list(knitr_current_input = knitr::current_input()))
3128
cat(knitr::knit_child("mod-date.Rmd", quiet = TRUE, envir = mod_date_envir))
3229
```
3330

34-
[**Mirai Solutions**](https://mirai-solutions.ch/) is a Zurich-based software development and consultancy firm, delivering cutting-edge technology and best practices to the industry, helping companies elevate their data analytics and operations.
31+
[**Mirai Solutions**](https://mirai-solutions.ch/){target="_blank"} is a Zurich-based software development and consultancy firm, delivering cutting-edge technology and best practices to the industry, helping companies elevate their data analytics and operations.
3532

3633
We are an interdisciplinary team of data scientists, software engineers, business consultants and IT architects with specialist knowledge ranging from finance and risk management to math/stats techniques to software development and project management.
3734

@@ -49,4 +46,4 @@ In this e-book, we share technical guidelines, how-tos and best practices around
4946

5047
![Python Logo](python-logo-only.png)
5148

52-
If instead you are more interested in **Python**, you can access our free Python training material [**here**](https://mirai-solutions.ch/py-techguides).
49+
If instead you are more interested in **Python**, you can access our free Python training material [**here**](https://mirai-solutions.ch/py-techguides){target="_blank"}.

renv.Rmd

+3-3
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ mod_date_envir <- list2env(list(knitr_current_input = knitr::current_input()))
99
cat(knitr::knit_child("mod-date.Rmd", quiet = TRUE, envir = mod_date_envir))
1010
```
1111

12-
For production readiness --- and project safety --- it is important to control the dependencies of a piece of development. This can be done at project level using the package [`renv`](https://rstudio.github.io/renv/).
12+
For production readiness --- and project safety --- it is important to control the dependencies of a piece of development. This can be done at project level using the package [`renv`](https://rstudio.github.io/renv/){target="_blank"}.
1313

1414
In an `renv` project, dependencies are resolved and tracked in a lock-file. As a new R session starts, `renv` detects whether installed dependencies are out of sync compared to the lock-file, ensuring the same virtual environment applies each time the project is opened.
1515

@@ -27,7 +27,7 @@ install.packages("renv")
2727

2828
## Set-up an `renv` project
2929

30-
In order resolve and track dependencies of a project, `renv` needs to discover what the required packages are. Although `renv` supports discovering dependencies by scanning all files in the project (_implicit mode_), we strongly advise to define the required dependencies in a `DESCRIPTION` file, and rely on `renv`'s _explicit mode_ (see ['Snapshot types'](https://rstudio.github.io/renv/reference/snapshot.html#snapshot-types) in the documentation for details).
30+
In order resolve and track dependencies of a project, `renv` needs to discover what the required packages are. Although `renv` supports discovering dependencies by scanning all files in the project (_implicit mode_), we strongly advise to define the required dependencies in a `DESCRIPTION` file, and rely on `renv`'s _explicit mode_ (see ['Snapshot types'](https://rstudio.github.io/renv/reference/snapshot.html#snapshot-types){target="_blank"} in the documentation for details).
3131

3232
To initialize `renv` for a project where dependencies are explicitly stated in the `DESCRIPTION` file, run:
3333

@@ -93,7 +93,7 @@ If the `DESCRIPTION` file does not request a specific package version, `renv` wi
9393
options(repos = "https://packagemanager.posit.co/cran/2024-01-02")
9494
```
9595

96-
Date-based CRAN snapshots have built-in support in `renv` with [`renv::checkout()`](https://rstudio.github.io/renv/reference/checkout.html), w/o the need for `(options(repos = ...))`:
96+
Date-based CRAN snapshots have built-in support in `renv` with [`renv::checkout()`](https://rstudio.github.io/renv/reference/checkout.html){target="_blank"}, w/o the need for `(options(repos = ...))`:
9797

9898
```{r , echo = TRUE, eval = FALSE}
9999
# check out packages from PPM using the date '2023-01-02'

roxygen-guidelines.Rmd

+5-5
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ This is based on:
2020

2121
- **roxygen2** vignettes: `browseVignettes("roxygen2")`, in particular
2222
[Generating Rd
23-
files](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html).
24-
- The [tidyverse style guide](https://style.tidyverse.org/documentation.html).
23+
files](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html){target="_blank"}.
24+
- The [tidyverse style guide](https://style.tidyverse.org/documentation.html){target="_blank"}.
2525
- Package development experience.
2626

2727
Examples are provided to show the concrete application of the described
@@ -94,7 +94,7 @@ bottom and in this order.
9494
- For **un-exported** objects documented for internal purposes, specify
9595
`@keywords internal` instead of `@export`.
9696
- Use
97-
[**markdown**](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd-formatting.html):
97+
[**markdown**](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd-formatting.html){target="_blank"}:
9898
If not done at package level, `@md` should be the last element (so it can easily
9999
be removed when moving to package-level).
100100
- Do not use `@rdname` if not documenting multiple objects (see below).
@@ -135,7 +135,7 @@ Several techniques and tools are available to enable and support a more
135135
consistent and maintainable documentation.
136136

137137
This can be described in detail in the [Do repeat
138-
yourself](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html#do-repeat-yourself)
138+
yourself](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html#do-repeat-yourself){target="_blank"}
139139
section of vignette _Generating Rd files_, and are summarized as follows
140140

141141
- Cross-link documentation files with `@seealso` and `@family`.
@@ -174,7 +174,7 @@ man-roxygen/ex-<FUNCTION_NAME>.R`.
174174

175175
Tags `@rdname` and `@describeIn` are a convenient way to document multiple
176176
functions in the same file. See the roxygen2 vignette [Generating Rd
177-
files](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html)
177+
files](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html){target="_blank"}
178178
(`vignette("rd", package = "roxygen2")`) for more detail.
179179

180180
In both case, not that `@title` should be specified only for the _main_

0 commit comments

Comments
 (0)