Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error thrown when using a Step from a Definition with an optional parameter #96

Closed
nextlevelbeard opened this issue Sep 30, 2022 · 2 comments · Fixed by #97
Closed

Error thrown when using a Step from a Definition with an optional parameter #96

nextlevelbeard opened this issue Sep 30, 2022 · 2 comments · Fixed by #97

Comments

@nextlevelbeard
Copy link

👓 What did you see?

Error is thrown when a valid step is described in a Scenario:

[Error - 6:01:37 PM] Request textDocument/semanticTokens/full failed.
  Message: Request textDocument/semanticTokens/full failed with message: Incomplete group: {"children":[]}
  Code: -32603

✅ What did you expect to see?

No errors.

📦 Which tool/library version are you using?

Extension version 1.3.0

🔬 How could we reproduce it?

With the following valid Step Definition:

Then(/I should( not)? be on the map/i, async (not) => { })

and the Step I should be on the Map :

Feature: Bug Report

  Scenario: User reports a bug
    Then I should be on the Map

📚 Any additional context?

The step definition is valid and made to support a positive and negative case.

Both I should be on the Map and I should not be on the Map are valid steps.

However, the error is only thrown with the positive case: I should be on the Map

@mindbraker
Copy link

Unfortunately I've stumbled across this error today with the same scenario described by @nextlevelbeard

[Error - 3:13:38 PM] Request textDocument/semanticTokens/full failed.
  Message: Request textDocument/semanticTokens/full failed with message: Incomplete group: {"children":[]}

@aslakhellesoy
Copy link
Contributor

Thanks for the detailed bug report @nextlevelbeard!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants