Run styler::style_pkg()
to make code formatting more consistent
#160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR runs
styler::style_pkg()
to style the codebase (according to the tidyverse specs). I am introducing this PR because:By running
styler::style_pkg()
I am attempting to create a baseline and ensure that future contributions can be confident. In case this is not desirable, I would like to request explicit documentation as to what code style is applied (e.g., in the package vignette). I realize we do not have hard standards on this in the blueprints at this time, and I do think there is value in a consistent and clear code style for the code, the maintainer, and for the contributors.