You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
The text was updated successfully, but these errors were encountered: