Gorkem Ercan

We are going to have to make the dependency update sooner or later. @aeschli, any hints if we can expect a resolution to https://github.com/microsoft/vscode-json-languageservice/issues/123 soon?

I do not see a problem with adding this option—definitely a better choice than post-processing. The fastest way to implement this would be to provide a PR on it. Let...

I think this should be implemented on the markdown extension to [request forward ](https://code.visualstudio.com/api/language-extensions/embedded-languages#request-forwarding)front-matter language requests to vscode-yaml.

@shsuman Do not fork or publish the yaml LSP with your own extension such things usually breaks our functionality. We have already had similar [cases](https://github.com/redhat-developer/vscode-yaml/issues/404) with different MSFT teams. I...

@shsuman Our release cycles are not synchronized, you probably are not going to refresh the LSP as often as we do. We end up with getting bug reports for all...

@shsuman Currently we have APIs to provide schemas dynamically that will allow the YAML LS to provide validation code assist etc. We do support a few JSON schema extensions too....

@JPinkney Do you have reference to the extension API and JSON schema extensions that we support. I thought it was a package on npm but I could not find it.

@shsuman pinged @JPinkney he reminded me where we recorded things take a look at https://github.com/redhat-developer/vscode-yaml/wiki/Extension-API

I do not grok why you would need to run your own copy of the LS, if you are trying to have **additional** diagnostics or completions. You can register multiple...

@evidolob while I was trying to pickup the fix for the failure for this I noticed that I can not rebase `parser-switch` to master/main anymore.