Skip to content

Commit a8feea9

Browse files
Merge pull request #754 from lorenzwalthert/documentation
- More docs (#754).
2 parents 4dfdd03 + 46be6df commit a8feea9

File tree

3 files changed

+22
-7
lines changed

3 files changed

+22
-7
lines changed

NEWS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
- Documentation overhaul: New README, new "Get started" pkgdown page, new
3636
vignettes on `strict = FALSE`, `Adoption` renamed to `Third-party
3737
integrations`, minor other doc improvements (#741, #643, #618, #614, #677,
38-
#651, #667, #672, #687, #752).
38+
#651, #667, #672, #687, #752, #754).
3939

4040
- `@exampleIsf` roxygen tag for conditional examples is now supported (#743).
4141

R/rules-spaces.R

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -232,12 +232,18 @@ set_space_between_levels <- function(pd_flat) {
232232
#' Start comments with a space
233233
#'
234234
#' Forces comments to start with a space, that is, after the regular expression
235-
#' "^#+'*", at least one space must follow if the comment is *non-empty*, i.e
235+
#' `#+['\\*]`, at least one space must follow if the comment is *non-empty*, i.e
236236
#' there is not just spaces within the comment. Multiple spaces may be legit for
237237
#' indention in some situations.
238+
#' @section Exceptions:
239+
#' Spaces won't be added to comments when they are:
240+
#'
241+
#' * shebangs
242+
#' * code chunk headers
243+
#' * xaringan markers
244+
#'
238245
#' @param pd A parse table.
239-
#' @param force_one Whether or not to force one space or allow multiple spaces
240-
#' after the regex "^#+'*".
246+
#' @param force_one Whether or not to force one space or allow multiple spaces.
241247
#' @importFrom purrr map_chr
242248
#' @keywords internal
243249
start_comments_with_space <- function(pd, force_one = FALSE) {

man/start_comments_with_space.Rd

Lines changed: 12 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)