Support for textDocument/InlayHint

[angelozerr]

Support for textDocument/InlayHint

Fixes #595

Signed-off-by: azerr azerr@redhat.com

[angelozerr]

This PR requires redhat-developer/vscode-quarkus#474

[angelozerr]

Here the result:

It display Java type before the alias.

It's just a POC and it doesn't use the real InlayHint of LSP4J but uses the structure like described in the spec.

The inlay hint doesn't appear when the Java type is not resolved. So you must type something in the text editor to refresh the inlay hint.

[rgrunber]

Nice :)

Only 2 things immediately stand out.

1. We should think about the best place to put the hint. Todo todo or todo Todo, or maybe todo : Todo, or todo (Todo). Basically it might cause some confusion if it just appears there.
2. I would play around with typing out the full line and confirm it isn't annoying if the hint appears as someone is typing. Somtimes the logic can resolve a hint at various points that causes the cursor to jump.

[angelozerr]

@rgrunber here the new renderer:

[fbricon]

please don't use package org.eclipse.lsp4j.proposed; this is not an eclipse project nor is it code copied from an eclipse project.

[angelozerr]

please don't use package org.eclipse.lsp4j.proposed; this is not an eclipse project nor is it code copied from an eclipse project.

rename with com.redhat.lsp4j.proposed. Once LSP4J will provide Inlay Hint, we will able to remove those classes.

[angelozerr]

Here a new demo with inlay hint:

Now I support only section parameter (and method parameter type has been removed, we will see in an another PR the method parameter name support).

This PR requires redhat-developer/vscode-quarkus#474 which provide settings to enable/disable inlay hints + provide inlay hint TypeScript by waiting for the release of vscode-languageclient which will provide this feature.

[AlexXuChen]

LGTM, working as intended

[angelozerr]

Thanks @AlexXuChen for the review!