Skip to content

Commit 093c6a1

Browse files
clarify vignette
1 parent 475a391 commit 093c6a1

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

vignettes/customizing_styler.Rmd

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ There are three major steps that styler performs in order to style code:
2323
2. Apply transformer functions at each level of the nested parse table. We use a
2424
visitor approach, i.e. a function that takes functions as arguments and
2525
applies them to every level of nesting. You can find out more about it on
26-
the help file for `visit`. Note that the function is not exported by styler.
26+
the help file for `visit()`. Note that the function is not exported by styler.
2727
The visitor will take care of applying the functions on every
2828
level of nesting - and we can supply transformer functions that operate on
2929
one level of nesting. In the sequel, we use the term *nest* to refer to
@@ -52,7 +52,7 @@ names(tidyverse_style())
5252
str(tidyverse_style(), give.attr = FALSE, list.len = 3)
5353
```
5454

55-
We note that there are different types of transformer functions. `filler`
55+
We note that there are different types of transformer functions. `initialize`
5656
initializes some variables in the nested parse table (so it is not actually a
5757
transformer), and the other elements modify either spacing, line breaks or
5858
tokens. `use_raw_indention` is not a function, it is just an option. All
@@ -286,3 +286,5 @@ removes line breaks before the curly opening bracket looks as follows:
286286
styler:::remove_line_break_before_curly_opening
287287
```
288288

289+
With our example function `set_line_break_before_curly_opening()` we don't need
290+
to worry about that as we are only adding line breaks, but we don't remove them.

0 commit comments

Comments
 (0)