Currently inline type hints are rendered as follows missing any spacing to the variable name:
Which esp. in line 17 becomes difficult to read. In the Java Editor inline hints are suffixed with a white space. If LSP4e behaves like this, the same code would look like this:
Responsible for inline type hints is org.eclipse.lsp4e.operations.inlayhint.LSPLineContentCodeMining
If I override the LineContentCodeMining#setLabel method and add a whitespace to the end of the label, I get the desired effect:
Currently inline type hints are rendered as follows missing any spacing to the variable name:![image](https://github.com/eclipse/lsp4e/assets/426959/320f42a8-8ee1-4ace-b132-413fffa53864)
Which esp. in line 17 becomes difficult to read. In the Java Editor inline hints are suffixed with a white space. If LSP4e behaves like this, the same code would look like this:
Responsible for inline type hints is
org.eclipse.lsp4e.operations.inlayhint.LSPLineContentCodeMining
If I override the
LineContentCodeMining#setLabel
method and add a whitespace to the end of the label, I get the desired effect:@mickaelistria @rubenporras Is this an adequate way to address this issue?