We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
a separate, minor issue with lintr:::is_valid_regex: lintr:::is_valid_regex(lintr::default_settings$exclude_linter) # FALSE
a separate, minor issue with lintr:::is_valid_regex:
lintr:::is_valid_regex
lintr:::is_valid_regex(lintr::default_settings$exclude_linter) # FALSE
Hmm, that's just because is_valid_regex() uses perl = FALSE, it works with perl = TRUE:
is_valid_regex()
perl = FALSE
perl = TRUE
!inherits(tryCatch(grepl(lintr::default_settings$exclude_linter, "", perl = TRUE), condition = identity), "condition") # [1] TRUE
Originally posted by @MichaelChirico in #2374 (comment)
Ultimately parse_exclusions() is running rex::re_matches(), which in turn runs perl = TRUE.
parse_exclusions()
rex::re_matches()
The text was updated successfully, but these errors were encountered:
# nolint:
Successfully merging a pull request may close this issue.
Hmm, that's just because
is_valid_regex()
usesperl = FALSE
, it works withperl = TRUE
:Originally posted by @MichaelChirico in #2374 (comment)
Ultimately
parse_exclusions()
is runningrex::re_matches()
, which in turn runsperl = TRUE
.The text was updated successfully, but these errors were encountered: