Javadoc popover when editing application.properties lacks context and can be confusing

[wilkinsona]

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.

[spring-projects-issues]

(comment in Pivotal Tracker added by Alex Boyko:)

I doubt will be able to eliminate @since part... We could add a link to container java type for example. I've done that for sts4 LS.

[wilkinsona]

I wasn’t suggesting that the @since part should be eliminated. That was just an example of why the lack of context is confusing. If it were clear that the popover is showing Jackson’s javadoc, it would be clearer that the @since is a Jackson version.

[spring-projects-issues]

(comment in Pivotal Tracker added by Alex Boyko:)

I suppose we'd need the following to give it more context:

Type link
Java element signature (?)
------------------------------------
Javadoc
------------------------------------
Classpath Entry container

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.