Manage client snippet on server side

[angelozerr]

Today snippet are managed on client side, but it doesn't take care of the classpath. For instance you have qj in the completion (Configure a Jaeger tracer) although your project could not have Quarkus Jaeger dependency.

I think JDT LS provides now a support for Eclipse template, we should manage snippet with Eclipse template (on server side) and I think we could check if the project has Jaeger dependency.

[fbricon]

This requires allowing for template contributions on the jdt.ls side, which is not opened yet.

[angelozerr]

Yes sure @fbricon it's just an idea for the future.

[angelozerr]

@fbricon I did that in my POC with maven XML extension (for dependencies). I think we can have a generic SnippetRegistry which manage any JSON vscode snippet on server side but with a context condition. I did that

• https://github.com/angelozerr/lsp4xml-extensions-maven/blob/master/org.eclipse.lsp4xml.extensions.maven/src/main/java/org/eclipse/lsp4xml/extensions/maven/MavenCompletionParticipant.java#L44
• which uses vscode snippets https://github.com/angelozerr/lsp4xml-extensions-maven/blob/master/org.eclipse.lsp4xml.extensions.maven/src/main/resources/org/eclipse/lsp4xml/extensions/maven/pom-snippets.json

In Quarkus context, the condition is the extension name.

[angelozerr]

An another usecase is for completion value, those snippets should not appear:

Managing snippet on server side will fix that too.