Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

brace_linter() always allows {}/{ } #1685

Merged
merged 3 commits into from
Oct 12, 2022
Merged

brace_linter() always allows {}/{ } #1685

merged 3 commits into from
Oct 12, 2022

Conversation

MichaelChirico
Copy link
Collaborator

Closes #1346

I skipped adding new examples for now. I'm a bit loath to do so while the actual style guidance is an open issue.

@codecov-commenter
Copy link

Codecov Report

Merging #1685 (63be9c4) into main (866b974) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1685   +/-   ##
=======================================
  Coverage   98.71%   98.71%           
=======================================
  Files         104      104           
  Lines        4498     4499    +1     
=======================================
+ Hits         4440     4441    +1     
  Misses         58       58           
Impacted Files Coverage Δ
R/brace_linter.R 100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow { } or {} in brace_linter independently of allow_single_line?
3 participants