Siddharth Sharma

I have observed similar behavior in an under development emacs-lsp/lsp-mode#4355 plugin, so it seems that behavior lies within TypeFox/yang-lsp.

Since the YANG LSP yang.settings supports // comments, it would be good to classify it as "JSON with Comments" to allow for documentation of the settings

@dhuebner any idea on this issue?

@dhuebner request your team's support here An immediate help would be clarification on following * what LSP message content/trigger results in `yang.settings` file being read by the language server *...

@dhuebner thanks for the initiation. I think something goes sideways relatively in the other LSP client sequence that "Language server will start building the workspace (loading *.yang files)" does not...

> Could we please have an option implemented in yang-vscode to log verbosely, as a cheaper alternate to code digging? Created https://github.com/TypeFox/yang-vscode/issues/92 for LSP client side aspects @dhuebner closed TypeFox/yang-vscode#92...

@dhuebner it was rather for even the latest and greatest Yangster/yang-vscode extension to use an unreleased (new/development) yang-lsp/yang-language-server as one use case, and to use an older yang-language-server with latest...

@dhuebner to ease the approach for what you suggest, may the *.vsix file be generated as part of build and release tasks? Anyhow, given that the LSP language servers are...

Hello @dhuebner, I have a related issue on TypeFox/yang-lsp#228 where it is requested to refine the diagnostic to match the RFC, as it is allowed to import yang-version 1.1 models...

Thanks @dhuebner, I have discussed with Rim and this is rather an independent engagement from my side hence it should not not interfere. I may provide a draft PR for...