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

infix_spaces_linter() accepts parse tags #2125

Merged
merged 11 commits into from
Sep 9, 2023
Merged

infix_spaces_linter() accepts parse tags #2125

merged 11 commits into from
Sep 9, 2023

Conversation

MichaelChirico
Copy link
Collaborator

Closes #1977

@codecov-commenter
Copy link

codecov-commenter commented Sep 8, 2023

Codecov Report

Merging #2125 (124da9c) into main (78417b0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head 124da9c differs from pull request most recent head 239ee52. Consider uploading reports for the commit 239ee52 to get more accurate results

@@           Coverage Diff           @@
##             main    #2125   +/-   ##
=======================================
  Coverage   99.65%   99.65%           
=======================================
  Files         121      121           
  Lines        5258     5260    +2     
=======================================
+ Hits         5240     5242    +2     
  Misses         18       18           
Files Changed Coverage Δ
R/infix_spaces_linter.R 100.00% <100.00%> (ø)

@AshesITR AshesITR merged commit 4a42798 into main Sep 9, 2023
@AshesITR AshesITR deleted the infix-node branch September 9, 2023 19:12
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.

infix_spaces_linter lacks a way to specify different rules for different = (EQ_ASSIGN, EQ_SUB, and EQ_FORMALS)
3 participants