Vladislav Frolov

- If the template string contains an expression longer than N characters, then the expression must be moved to a separate variable.

Bug in WRONG_NEWLINES

3

Example: ``` vall foo = (hasExplicitNotUnitReturnType || isFunWithExpressionBody && !hasExplicitUnitReturnType && hasNotExpressionBodyTypes) && !hasReturnKdoc && !isReferenceExpressionWithSameName ``` Diktat will glue two lines into one and break on warning LONG_LINE

CONSTANT_UPPERCASE breaks the code.

1

In fixed mode, this rule changes the constant to uppercase. But does not change these constants themselves in the code, thereby making the code not working

Bug in UNUSED_IMPORT

5

Sometimes the warning UNUSED_IMPORT doesn't fire

Diktat doesn't swear at commented code ``` /* companion object : RStatics( RegistrationView::class ) { init { RegistrationView.contextType = requestStatusContext } }*/ ```

Unity project for the Welcome to the Moon board game. [Welcome-To-The-Moon-Companion](https://github.com/Cheshiriks/Welcome-To-The-Moon-Companion) is a companion app for independently completing all 8 scenarios of the board game Welcome to the Moon. 

Unused imports with * are not removed 

[FILE_NAME_INCORRECT] suggestion for improvement

3

If the file contains only one Interface or enum class, then it will not have a **.kt** in the name. Maybe add this to the rule?

[`TOO_MANY_LINES_IN_LAMBDA`] Can we configure this rule somehow to not to trigger on frontend?

1

can we configure this rule somehow to not to trigger on frontend? _Originally posted by @kgevorkyan in https://github.com/saveourtool/save-cloud/pull/2099#discussion_r1173818369_ > We can only adjust the maximum size of the lamda itself....

Closes #2953