Inline code

05

# Inline code
---

# <center>Inline code</center>

1

???
Combining code with text!!

---

# <center>Inline text formatting</center>

A single back tick denotes a `function` and changes the format

A single back tick with r denotes code to be run in R
``` `r top_viewers %>% pull(episode)` ```

]

???
The following code will run from a dataset generated in the previous section of Code Chunks:

```r
top_viewers <- ratings %>% 
 filter(series == 1) %>% 
 top_n(1, viewers_7day)

```

Same word: `function`

The top viewed episode in series 1 was episode
5

]

???
Inline code can be formatted on screen to be on multiple lines and will still run but the colouring changes:

and automatically indent formatting is lost. It's not a good idea to have a lot of code in inline for ease of debugging.

---

# <center>Inline code - in the YAML</center>

2

---
class: your-turn

# Your turn

In the file `01-bakeoff-report.Rmd`

1 Add the following in the YAML and 🧶 **Knit**

```yaml
---
date: '2022-01-01'
---
```

2 Replace the date with this code

```yaml
---
date: '`r Sys.Date()`'
---
```

3 Replace the date with this code

```yaml
---
date: '`r lubridate::today()`'
---
```

???
The quotation marks are very important, particularly with the inline code starting `r`

---
class: your-turn

# Answers

1. The date appears as we'd expect underneath the main title

1. Although the date is still in the YAML it is overwritten by the YAML code chunk to today's date

1. The date is the same but this uses a function with a more user-friendly name - which do you prefer?

---

# <center>Inline code - formatting in the YAML</center>

3

---

# <center>Friendly date formats</center>

```r
"`r format(Sys.time(), '%d %B %Y')`"
```
]

![Screenshot of the date format being date, month in full and the year](images/format-date-yaml.PNG)

]

---
class: inverse

# <center>Next section...</center>