SA1107: Dont report if the previous statement is missing its last token #1543
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.
I know this is pedantic, but it was a little bit annoying. When writing a statement that has its last token missing (e.g. a missing semicolon) SA1107 is reported in the following statement. The reason is that roslyn puts the missing semicolon at the start of the next line. So SA1107 is reported because the next statement is on the same line as the missing semicolon. In this code the whole if statement has squiggles. With this change SA1107 is not reported if the last token of the previous statement is missing.