Fix indentation in generated step definition classes #144
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.
Generated step definition classes had closing braces incorrectly concatenated on the same line, producing malformed code like
} }for block-scoped namespaces and}}for file-scoped namespaces.Root cause: The code generator used
StringBuilder.Append()instead ofAppendLine()when appending the step definition snippet, causing the class closing brace to appear on the same line as the method's closing brace.Changes:
DefineStepsCommand.cs: Changedtemplate.Append(adjustedSnippet)totemplate.AppendLine(adjustedSnippet)inGenerateStepDefinitionClass()Before:
After:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.