explicit parse_settings = TRUE - #706
Merged
Merged
Conversation
Contributor
Author
|
I'm unsure how the maintainers (I guess @renkun-ken @randy3k) want to proceed with this PR. Do you want me to bring this PR into a state so it can be merged, and what steps would that entail? Or would you rather implement a fix yourself (totally fine by me!)? |
Contributor
|
@ManuelHentschel Sorry for bothering you, but could you take a look at this? |
|
In the absence of updates, see a workaround in: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
According to https://github.com/r-lib/lintr/releases with lintr 3.3.0-1:
This means
.lintrfiles are ignored for the linting vscode does in the background by default. Explicitly settingparse_settings = TRUE(as suggested in this PR) helps.