[bean completion proposals] completion proposals show up at higher priority than regular Java proposals

[martinlippert]

In certain situations, bean completion proposals show up at a higher priority than regular Java completion proposals (even if the prefix doesn't really match) and therefore interfere with the regular Java completions in a horrible way. This was observed in Eclipse first, but the same problem happens in VSCode as well.

Example:

@Bean
public BeanOne beanOne() {
	BeanOne beanOne = new BeanOne();
	bean<*>
	return beanOne;
}

It is very likely that the user would like to auto-complete to beanOne from the line above and continue to use that, but the first completion that shows up is the option to auto-wire a bean with name beanOne.

The quick workaround is to disable the bean completion proposals in the preferences:

• Eclipse: Preferences -> Spring -> Inject Bean completion proposals in Java editor
• VSCode: Settings -> Preferences -> Spring Boot Tools -> Features -> Inject-Bean

[BoykoAlex]

Should be fixed with Boot LS and LSP4E changes