-
Notifications
You must be signed in to change notification settings - Fork 230
/
workflow-scripts.Rmd
45 lines (28 loc) · 1.29 KB
/
workflow-scripts.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
---
output: html_document
editor_options:
chunk_output_type: console
---
# Workflow: scripts {#workflow-scripts .r4ds-section}
## Exercise 6.1 {.unnumbered .exercise data-number="6.1"}
<div class="question">
Go to the RStudio Tips twitter account, <https://twitter.com/rstudiotips> and find one tip that looks interesting.
Practice using it!
</div>
<div class="answer">
The current timeline of [\@rstudiotips](https://twitter.com/rstudiotips) is displayed below.
<a class="twitter-timeline" href="https://twitter.com/rstudiotips?ref_src=twsrc%5Etfw"> Tweets by rstudiotips</a>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
</div>
## Exercise 6.2 {.unnumbered .exercise data-number="6.2"}
<div class="question">
What other common mistakes will RStudio diagnostics report?
Read <https://support.rstudio.com/hc/en-us/articles/205753617-Code-Diagnostics> to find out.
</div>
<div class="answer">
You should read that page, but some other diagnostics for R code include the following.
1. Check for missing, unmatched, partially matched, and too many arguments to functions.
1. Warn if a variable is not defined.
1. Warn if a variable is defined but not used.
1. Check that the code style conforms to the [tidyverse style guide](https://style.tidyverse.org/).
</div>