-
Notifications
You must be signed in to change notification settings - Fork 185
Issues: r-lib/lintr
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Exclude should ignore groups
bug
an unexpected problem or unintended behavior
#2831
opened Mar 11, 2025 by
WetRobot
Error in repeat_linter with unexpected object spacing
bug
an unexpected problem or unintended behavior
#2828
opened Mar 10, 2025 by
MichaelChirico
False positive/negative lints with "natural" comments
false-negative
code that should lint, but doesn't
false-positive
code that shouldn't lint, but does
#2827
opened Mar 10, 2025 by
MichaelChirico
Some linters get garbled metadata with "unexpected" comments
bug
an unexpected problem or unintended behavior
lint-metadata
#2826
opened Mar 10, 2025 by
MichaelChirico
matrix_apply_linter() fails with interweaved comments
bug
an unexpected problem or unintended behavior
#2825
opened Mar 10, 2025 by
MichaelChirico
literal_coercion_linter() fails with interweaved comments
bug
an unexpected problem or unintended behavior
#2824
opened Mar 10, 2025 by
MichaelChirico
Should assignments be excluded from undesirable_function_linter?
false-positive
code that shouldn't lint, but does
#2815
opened Mar 5, 2025 by
MichaelChirico
R6 method chaining
false-positive
code that shouldn't lint, but does
indentation ๐
#2813
opened Mar 4, 2025 by
b-rhodes
get_source_expressions() should get a way to parse encodings directly
blocked-internal
Fulfillment of this issue is blocked until another lintr issue is finished
feature
a feature request or enhancement
#2806
opened Mar 3, 2025 by
MichaelChirico
New linter for
...names()
instead of names(list(...))
new-linter
#2794
opened Feb 26, 2025 by
m-muecke
Migrate stopifnot() usages to cli_abort()
consistency ๐ ๐
internals
Issues related to inner workings of lintr, i.e., not user-visible
#2793
opened Feb 25, 2025 by
MichaelChirico
lint a feature request or enhancement
case_when()
that could use the levels(x) ~ value approach
feature
#2774
opened Feb 21, 2025 by
olivroy
Decide if we actually need our version of %||% or it should just the base version
internals
Issues related to inner workings of lintr, i.e., not user-visible
#2768
opened Feb 20, 2025 by
MichaelChirico
Should a feature request or enhancement
$xml_find_function_calls()
be friendlier for non-syntactic calls like %%
(x, y)?
feature
#2760
opened Feb 18, 2025 by
MichaelChirico
unnecessary_lambda_linter() misses '!' when suggesting removing a lambda
false-positive
code that shouldn't lint, but does
Detection of variable usage prior to assignment in function scope
blocked-external
Issues that are blocked by something outside of lintr's direct control
object linters ๐
#2739
opened Feb 12, 2025 by
immanuelazn
Clean-up: use expect_no_lint() where appropriate
internals
Issues related to inner workings of lintr, i.e., not user-visible
#2737
opened Feb 12, 2025 by
MichaelChirico
Ship a static .gif file with the CRAN README
internals
Issues related to inner workings of lintr, i.e., not user-visible
rhub::check_for_cran() no longer works
internals
Issues related to inner workings of lintr, i.e., not user-visible
Possibly remove <<- from the default valid operators in assignment_linter
blocked-external
Issues that are blocked by something outside of lintr's direct control
breaking change โ ๏ธ
API change likely to affect existing code
consistency ๐ ๐
object_usage_linter fails to account for withr-defined names
false-positive
code that shouldn't lint, but does
object linters ๐
#2714
opened Feb 4, 2025 by
MichaelChirico
Un-braced nested if/else gives false positive for unreachable_code_linter
false-positive
code that shouldn't lint, but does
#2710
opened Jan 21, 2025 by
MichaelChirico
Update the pipe_consistency_linter() default to be '|>'?
breaking change โ ๏ธ
API change likely to affect existing code
#2707
opened Jan 14, 2025 by
MichaelChirico
Previous Next
ProTip!
Add no:assignee to see everything thatโs not assigned.