-
Notifications
You must be signed in to change notification settings - Fork 125
Javadoc popover when editing application.properties lacks context and can be confusing #265
Comments
(comment in Pivotal Tracker added by Alex Boyko:) I doubt will be able to eliminate |
I wasn’t suggesting that the |
(comment in Pivotal Tracker added by Alex Boyko:) I suppose we'd need the following to give it more context:
Not sure if we could get those delimiters done nicely as they are shown in IntelliJ. If content looks fine I can start looking into this. |
(comment in Pivotal Tracker added by Martin Lippert:) I can see this being fixed in the old properties editor that we use in STS3 and partly in STS4, but I don't see the nice hover information in the language-server-based property editor when using that in Eclipse/STS4 distro. Can you double check? |
(comment in Pivotal Tracker added by Alex Boyko:) STS4/Eclipse hovers probably don't look at nice at STS3... I'll double check... if it's the same as in VSCode then this is it for now for (M12)... |
(comment in Pivotal Tracker added by Alex Boyko:) @mlippert This is how the hover looks for me. It's expected... for now... Maybe the signature will look JDTish soon (My PR for JDL LS just got merged, so we can grab the signature from JDT LS as well as javadoc content) |
When editing application.properties, a useful popover is shown that helps to complete a key. When part of the key is an enum, for example,
spring.jackson.serialization.*
, the popover displays the javadoc for the enum's value. This javadoc is displayed without context so it's not clear that it's Jackson's javadoc that's being displayed.By contrast, the same popover in IDEA makes it clear that it's Jackson's javadoc that is being shown:
The context is important as it's useful to know where the javadoc is coming from. It's also important as it helps with things like
@since
information:I don't think it's clear that the 2.6 is a Jackson version.
The text was updated successfully, but these errors were encountered: