You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This plugin does not respect docstring placement.
To Reproduce
Steps to reproduce the behavior:
Install the plugin with cucumberautocomplete.skipDocStringsFormat set to true.
Create this Gherkin file w/ with plugin installed:
Feature: Phrases
Scenario: 500 years later, people started using chickens for sacred events, sometimes eating them.
Given the text "500 years later, people started using chickens for sacred events, sometimes eating them."
Then the api returns:
"""
500 years later,
people
started
using
chickens
for sacred events,
sometimes eating
them.
"""
click save or otherwise trigger the plugin, and the text will format the DOCSTRING rightwards, breaking the test:
Feature: Phrases
Scenario: 500 years later, people started using chickens for sacred events, sometimes eating them.
Given the text "500 years later, people started using chickens for sacred events, sometimes eating them."
Then the api returns:
"""
500 years later,
people
started
using
chickens
for sacred events,
sometimes eating
them.
"""
Indentation of the opening """ is unimportant, although common practice is two spaces in from the enclosing step. The indentation inside the triple quotes, however, is significant. Each line of the Doc String will be dedented according to the opening """. Indentation beyond the column of the opening """ will therefore be preserved.
In my case I cannot write functional tests with the VSCode plugin enabled, as it overrides my placement of DOCSTRINGSs fully dedented. The behaviour I want is for Gherkin highlighting to exist without it touching DOCSTRING placement at all. As our team copies and pastes from these indented texts often, we have a valid reason to want the DOCSTRING fully dedented and placed leftwards for each test. Per the syntax spec, this is valid Gherkin.
Describe the bug
This plugin does not respect docstring placement.
To Reproduce
Steps to reproduce the behavior:
cucumberautocomplete.skipDocStringsFormat
set totrue
.Expected behavior
The Gherkin syntax spec clearly states that:
In my case I cannot write functional tests with the VSCode plugin enabled, as it overrides my placement of DOCSTRINGSs fully dedented. The behaviour I want is for Gherkin highlighting to exist without it touching DOCSTRING placement at all. As our team copies and pastes from these indented texts often, we have a valid reason to want the DOCSTRING fully dedented and placed leftwards for each test. Per the syntax spec, this is valid Gherkin.
Cucumberautocomplete part of VSCode settings:
The text was updated successfully, but these errors were encountered: