-
Notifications
You must be signed in to change notification settings - Fork 39
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
WRONG_INDENTATION
false-positive: "the same number of indents to the opening and closing quotes was expected"
#1490
Labels
Milestone
Comments
Originally from [saveourtool/save-cli/security/code-scanning/131] (https://github.com/saveourtool/save-cli/security/code-scanning/131), caused by 998d0e9 as a part of #811/#1364. The offending fragment is in val warnText = if (!difOffsetCloseAndOpenQuote) {
"the same number of indents to the opening and closing quotes was expected"
} else {
"expected $expectedIndent but was ${indentError.actual}"
} The minimal repro is val v = f(
"text $variable text".isEmpty()
) Analysis
|
0x6675636b796f75676974687562
changed the title
False-positive Wrong_Indentation:
Aug 9, 2022
the same number of indents to the opening and closing quotes was expected
WRONG_INDENTATION
false-positive: "the same number of indents to the opening and closing quotes was expected"
0x6675636b796f75676974687562
assigned 0x6675636b796f75676974687562 and unassigned Arrgentum
Aug 9, 2022
0x6675636b796f75676974687562
added a commit
that referenced
this issue
Aug 11, 2022
### What's done: * See #1490.
0x6675636b796f75676974687562
added a commit
that referenced
this issue
Aug 11, 2022
) ### What's done: * See #1490.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I believe, caused by 998d0e9
Observed behavior
https://github.com/saveourtool/save-cli/security/code-scanning/132
https://github.com/saveourtool/save-cli/security/code-scanning/131
Reproducible on diktat-demo with this snippet:
Environment information
The text was updated successfully, but these errors were encountered: