Add a new step implementation in a new file - the step is shown as unimplemented

[sswaroopgupta]

Expected behavior
Add a new step implementation in a new file - the step is shown as implemented

Actual behavior
Add a new step implementation in a new file - the step is shown as unimplemented

Steps to replicate

• Create a gauge-java project
• Add a new step
• Give the implementation in a new file
• Go back to the spec file
• Close the impl file.
• Go back to the spec file
• The step is shown as unimplemented

Version

Gauge version: 1.0.4.nightly-2018-12-03
Commit Hash: 62a48e5

Plugins
-------
java (0.7.0.nightly-2018-12-04)

Related issue getgauge/gauge-vscode#83

[negiDharmendra]

This issue is not just related to gauge-java, I can replicate this issue with gauge-js as well.
Something has changed(not sure yet, what that change is) either in VSCODE or VSCODE LSP client. Due to which the events our LSP server receives from vscode are not in the correct order while creating step implementation in the new file.

Expected order of events

1. textDocument/didOpen
2. workspace/didChangeWatchedFiles
3. textDocument/didChange
   which is correct in vscode-jsonrpc(3.6.0), vscode-languageclient(4.0.0) and vscode-languageserver-protocol(3.6.0)

Actual order of events

1. textDocument/didOpen
2. textDocument/didChange
3. workspace/didChangeWatchedFiles
   vscode-jsonrpc => 4.0.0
   vscode-languageclient => 5.1.1
   vscode-languageserver-protocol => 3.13.0

I have raised an issue on the vscode language server node.

[nehashri]

To fix this, there needs to be a change in the implementation of these requests in the runner. Here is a list of runners which support lsp protocol as of now and the PR's raised against them. This issue needs to be verified against each of these

Langauge	Nightly Date	Verified
Java	>= 17-01-2019
JavaScript	>= 18-01-2019
Python	>= 01-02-2019
Ruby	>= 23-01-2019
.Net core	>= 29-01-2019

[Debashis9012]

This is reproducible for dotnet language.

Gauge version: 1.0.5.nightly-2019-02-15
Commit Hash: 48d032f

Plugins
-------
dotnet (0.1.2.nightly-2019-02-14)

[gaugebot]

The fix should be available in nightly >= 21-2-2019

[Debashis9012]

This has been verified against the below version.
1.0.5.nightly-2019-02-22