Unbalanced braces reported if value contains double slash

[joe-mojo]

Describe the bug If a correctly closed string literal is holding a '//', next brace is reported as unmatched. Minimal example:

pipeline {
    agent none
    parameters {
        string(name: 'GIT_URL', defaultValue: 'https://example.com/repos/project.git', description: 'whatever')
    }

}

Expected behaviour As the double-slash are in correctly closed string literal, no error should be reported

Actual behaviour 2 braces are wrongly reported as unbalanced

Screenshots Actual behaviour: Workaround:

Additional context Workaround:

pipeline {
    agent none
    parameters {
        string(name: 'GIT_URL', defaultValue: 'https:/' + '/example.com/repos/project.git', description: 'whatever')
    }

}

Splitting string literal so as to remove the // sequence remove both reported errors.

[wolf99]

Seeing same issue

[tomas-kr]

Same issue, but no "//" required:

[ahochsteger]

@sgwozdz the bug seems to be also triggered by /* somewhere in a string like in this simple example:

node {
    stage('Test') {
        sh 'ls build/*.json'
    }
}

When removing the slash from the ls command, the error disappears:

It seems that to treat /* somewhere in a string as the start of a block comment just like //, causing the error.

BTW I'm using v1.1.0 of the extension with v1.73.1 of Visual Studio Code.

[MiMiMeowMeow]

Bump Still see this issue v1.1.0 of the extension with v1.91.1 of Visual Studio Code.