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

Go to definition does not work #25

Closed
uandrei opened this issue Jan 18, 2017 · 1 comment
Closed

Go to definition does not work #25

uandrei opened this issue Jan 18, 2017 · 1 comment
Assignees
Milestone

Comments

@uandrei
Copy link

uandrei commented Jan 18, 2017

Steps to reproduce:

  • create given.js file at path d:\Work\myapp\src\features\step_definitions\given.js
  • set in the .vscode/settings.json the following setting:
    {
    "cucumberautocomplete.steps": [
    "src\features\step_definitions"
    ]
    }
  • go in a feature file and select Go To Definition (F12) for a given statement

Expected outcome: VS Code will show me the code for that specific statement

Actual outcome: VS Code throws an error ("Unable to open 'given.js': File not found (\d:\Work\myapp\src\features\step_definitions\given.js'). The path is correct and the file exists in there. VS Code does not underline the given statement with green line, which means it does recognize where the source comes from, but cannot go to the definition.

@alexkrechik alexkrechik added this to the 2.0.0 milestone Jan 19, 2017
@alexkrechik alexkrechik reopened this Jan 21, 2017
@alexkrechik
Copy link
Owner

Please retest using 2.0.0

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

No branches or pull requests

2 participants