Consider showing completion item detail if available for all list items

[bmewburn]

Take the following completion list.

Each Client item belongs to a different namespace. If the completion item detail was shown immediately for each item then users could, at a glance, easily identify the relevant item out of a list of similarly labeled items. I suppose the argument against is that this can be done by modifying the label to include this, but then what is the role of the detail property?

[bmewburn]

Furthermore, if an extension author does try and add detail to the label to work around this limitation, then it can end up with incorrect highlighting as shown below.

[olafurpg]

Any pointers on how to contribute a fix displaying the "detail" field if it's available? This seems like a low-hanging fruit that would greatly improve the user experience in cases like below

[gabro]

As an extra data point, the Java LS works around this by including the package in the "label":

[bmewburn]

@gabro , when using the label do you find it can cause incorrect highlighting as in the example above, though?

[olafurpg]

@bmewburn the highlighting works out ok in my experience if you update the filter text to not include the appended namespace.

[jrieken]

fyi - I plan on implementing this for the next (Jan 2020) release and that "label + detail" workarounds will then look bad. Because of that we might start with having this behind a setting