Fix Semi-colon on inline methods after property declaration disappears #585
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.
fixes #560
An code example:
var n: Int = 0 /*C1*/ ; protected set
is aK.Property
.protected set
is a setter accessor in theK.Property
, it can be in a new line and then no semi-colon is required, but it can be in the same line and then a semi-colon is required as a delimiter.For the latter case with a semi-colon inside a
K.Property
, However, there is not a space room for/*C1*/
inK.Property
.This PR proposed to change variable declarations in
K.Property
from typeJ.VariableDeclarations
toJRightPadded<J.VariableDeclarations>
, plusSemiColon
marker, then this case can be handled.