Style code used in examples

[rjake]

Fixes #4092

This is my first PR for ggplot2. This will use the tidyverse style in the example code. I tried to check all docs. It was mentioned that a bigger audit might be done via styler at a later date and so I only picked a few types of coding style to change. If the code looked like this

 p + scale_fill_brewer(direction = -1) 

I left it be.
I only moved to new lines when there was more than one pipe present

 p + scale_fill_brewer(direction = -1) + theme_dark()

#becomes 
 p + 
  scale_fill_brewer(direction = -1) + 
  theme_dark()

when the arguments weren't indented under the parentheses, or when the line had two functions ggplot() + geom...

ggplot(mpg, aes(cty, hwy) + geom_point()

# becomes
ggplot(mpg, aes(cty, hwy) + 
  geom_point()

There were some updates that roxygen2 (dev version) made that I committed at the end

\item The default (\code{\link[scales:oob]{scales::censor()}}) replaces out of
\item The default (\code{\link[scales:censor]{scales::censor()}}) replaces out of bounds values with \code{NA}.

I also had 2 failed tests that seemed unrelated to my code changes

[clauswilke]

The sf tests don't fail in the continuous integration runs. If tests fail for you locally you may have to update sf.

[yutannihilation]

Thanks for the contribution!

There were some updates that roxygen2 (dev version) made that I committed at the end

You probably are using the older version of scales. These Rd files are now oob as of version 1.1.1, more precisely, since this commit:

r-lib/scales@e800430#diff-cf40208acff59ab6d96fa89d3c1f9a39

[yutannihilation]

@rjake Could you update scales package and regenerate the docs?

[yutannihilation]

Looks good to me! I added some comment on where another answer might be available, but they are just a matter of preferences so leave the questions for now.

[yutannihilation]

One question is a like break after <- should be added or not, but I think either is fine.

c.f. https://style.tidyverse.org/pipes.html#assignment-2

[yutannihilation]

This "text", can be placed in the same line of annotate(, but this is also fine.

Short unnamed arguments can also go on the same line as the function name, even if the whole function call spans multiple lines.
https://style.tidyverse.org/syntax.html#long-lines

[rjake]

I've noticed that Ctrl + Enter sometimes errors out at the bottom if the pattern is mismatched about code touching the parentheses or not

# fine
annotate("text", 
         label = "plot mpg vs. wt")

# fine
annotate(
  "text",
  label = "plot mpg vs. wt"
)

# not fine
annotate("text",
  label = "plot mpg vs. wt"
)

Here's an example

library(tidyverse)

mpg %>% 
  mutate(
    x1 = "ok here") %>% 
  mutate(
    x2 = "not ok") # use Ctrl + Enter in this line

[yutannihilation]

Hmm, thanks for the information. I hope this will be fixed on RStudio...

[yutannihilation]

Thanks!