fix: Generate formatted Python step definitions #161
Merged
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.
🤔 What's changed?
The Python step definition snippet has been modified as follows:
context
argument when the step has no parameters - removing redundant characters that would fail formatters such as blackExamples
When generating a Python step definition from a gherkin step...
...the step definition is indented by 2 spaces - which is invalid Python; and a space is present between the parentheses (
()
) and the colon (:
) of the function declaration.Additionally, when generating a Python step definition from a gherkin step containing no parameters...
Then I should have many cucumber
...a trailing comma and space appear after
context
.⚡️ What's your motivation?
Fixes #160, rendering formatted Python step definitions as follows:
And with multiple parameters as follows:
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
NA
📋 Checklist: