Go to custom command definition / Custom command not found

[thaianalps]

Bug or problem When I use "Cypress: Go to custom command definition" this message is displayed: "Custom command not found"

My .vscode/setting.js

{
    "cypressHelper.includeAnnotationForCommands": true,
    "cypressHelper.customCommandsFolder": "cypress/support",
    "cypressHelper.typeDefinitionFile": "cypress/support/customCommands.d.ts",
    "cypressHelper.fixtureAutocompletionCommands": [
        "fixture"
    ],
    "cypressHelper.menuItems": {
        "OpenSingleTest": true,
        "OpenSpecFile": true,
        "GenerateCustomCommandTypes": true,
        "GoToCustomCommand": true,
        "FindCustomCommandReferences": true,
        "FindStepDefinitionReferences": true
    },
}

Expected behavior I expected it to be forwarded to the custom command.

Environment ():

• Extension version: 4.766
• VS Code version: 1.45.4
• OS: Linux (Mint):

Prints:

[Shelex]

Hello @thaianalps Thank you for posting an issue with so well documented info!

It was not reproducing on OSX or Windows so I have checked VirtualBox with Linux Mint installation - and actually got it. That is because of sanitising absolute paths by removing trailing slashes. It seems that on linux distros the first slash is needed for accessing files, so I have provided a fix in version 0.6.2.

Could you please update and check if it works for you?

[thaianalps]

Worked perfectly!!!!

Thanks a lot!