Open daantimmer opened 8 months ago
It is possible to workaround the issue using:
{
"cucumberautocomplete.customParameters": [
{
"parameter": "\"(",
"value": "\""
},
{
"parameter": ")\"",
"value": "\""
}
]
}
This does mean every occurance of "(
and )"
within a regular expression would be replaced by "
.
Describe the bug C++11 introduced raw string literals. Which are the preferd method of writing regular expressions in C++. Raw string literals look like:
const char* str = R"(this is a raw string literal)";
. Raw string literals start withR"(
and end with)"
. Given the current tools provided by VSCucumberAutoComplete it is impossible to properly match raw string literal steps:To Reproduce Steps to reproduce the behavior:
(there is a step that is a raw string literal)
Expected behavior VSCucumberAutoComplete treats the above GIVEN step as capturing the whole string, which is incorrect. Example:![image](https://github.com/alexkrechik/VSCucumberAutoComplete/assets/8293597/da3bfcc8-ba58-4371-9003-31363664111e)
Screenshots See Expected Behaviour
Cucumberautocomplete part of VSCode settings:
Step definition: See above
Gherkin step line See above