src/NLog/Common/InternalLogger.cs (1)

388-433: Indentation inconsistency in the else branch (lines 425-430).

The string.Concat call at lines 425-430 uses different indentation compared to its counterpart at lines 405-411. The arguments in the non-timestamp else branch are indented by 4 spaces relative to return, while the timestamp branch aligns arguments under the opening parenthesis.

💅 Proposed fix for consistent indentation

             else
             {
                 if (ex is null)
                 {
                     return string.Concat(
                         level.ToString(),
                         fieldSeparator,
                         fullMessage);
                 }
                 else
                 {
                     return string.Concat(
-                    level.ToString(),
-                    fieldSeparator,
-                    fullMessage,
-                    " Exception: ",
-                    ex.ToString());
+                        level.ToString(),
+                        fieldSeparator,
+                        fullMessage,
+                        " Exception: ",
+                        ex.ToString());
                 }
             }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/NLog/Common/InternalLogger.cs` around lines 388 - 433, The CreateLogLine
method has inconsistent indentation in the non-timestamp else branch for the
string.Concat call; align the argument indentation to match the timestamp branch
style so the arguments are vertically aligned under the opening parenthesis
(same as the block that returns TimeSource.Current.Time.ToString(...)). Update
the string.Concat block in the else branch (the branch where IncludeTimestamp is
false and ex is not null) so its arguments (level.ToString(), fieldSeparator,
fullMessage, " Exception: ", ex.ToString()) follow the same indentation pattern
as the other string.Concat usages in CreateLogLine.