Code Completion in Javadoc Comments about moonshine-feathersui-text-editor

[joshtynjala]

I see some strange behavior for code completion in JavaDoc (/**) comments. @JustinProminic reported similar issues for /* and // comments, but I couldn't reproduce this.

I wonder if Justin accidentally added /** instead of /*, and that's why he saw some completion.

I think this is intentional, though. You can see that it gives me an option to generate an @link, which is something I use in Eclipse. Completing the class name could potentially be nice when writing the documentation as well.

Yes, this comes from the language server, and it appears to be intentional.

Continue typing "m.". Moonshine starts completion again, but shows nested classes, not methods or properties.

I have no idea why VSCode behaves differently here. There are indeed using the same language server.

It could be that different versions of the language server or different versions of the JDK provide slightly differing behaviors. The VSCode extension might be using a different default value for a setting than the language server. For reference, the language server is developed by Eclipse, while the VSCode extension is developed by Red Hat. It's possible that the teams have a disagreement on what should be default.

Regardless, this appears to be similar intentional behavior to me. I would be wary to consider it a bug. Even if you want to consider it a bug, I'm not sure how I would tell the language server to change this behavior. There probably aren't any settings for that level of granularity.

Create a JavaDoc comment. A closing */ is automatically added when you hit Enter

Moonshine's text editor supports "auto-closing pairs", but it looks like I haven't added any type of comments in the pairs specified in Moonshine's language syntax plugins. Only brackets so far. I may have simply forgotten to add them. I'll add this to my to-do list.

[JoelProminic]

Continue typing "m.". Moonshine starts completion again, but shows nested classes, not methods or properties.

The VSCode behavior for this case is fine if we want to stick with that. I could see both the VSCode and Eclipse behavior being annoying in some cases, so this may have just been a developer preference. I am a little out of date on Eclipse (2020-09), so that could also explain the difference.

I had some more thoughts about the comment completion, so I created #13.