Key Bugs Fixed
Navigation and Content Assist
A number of content assist glitches in Eclipse participants were fixed:
- Imports added during content assist could result in garbled code
- Mismatched case or additional characters typed during filtering would result in incorrect proposal text being inserted
- With an Eclipse host, and VS Code / browser clients, the labels of content assist proposals were sometimes matched with typed text
- With an Eclipse Neon host, content assist would not be available in clients
In VS Code, when editing Java, template proposals would sometimes not overwrite matched text.
In Eclipse, hyperlink navigation links would sometimes be hard to activate.
In IntelliJ, the go to definition action would not take you to the name of the targeted element, but to the beginning of the line on which the element was defined instead.
After inserting a proposal with no parameters, the cursor would jump to the location at which the content assist was invoked.
Project Structure and IDE Specific Issues
- If a project had two or more modules with the same content root name, the session would not start.
- If an active file was renamed, an IntelliJ client would freeze and sometimes not recover.
- On the host, closing a new unsaved file would result in it automatically reopening immediately. There was no ghost in the machine, it was just a bug in the code.
- When editors were tiled in IntelliJ and VS Code hosts, edits could go to the wrong location in the VS Code client.
- If different editors were being activated in quick succession, edits made by the client could be lost.
- For non-standard builds of VS Code like VS Codium, it may have been impossible to enable the “proposed API” mods we needed to enable advanced functionality.
- Renaming a file would error out, resulting in the file disappearing until the host opened it.
- When running with IBM’s J9 VM, Eclipse clients were unable to join sessions due to encryption issues with this VM.
- If an Eclipse client joined a session with no terminals, content from terminals that were subsequently shared would not be visible.
- Plugin is now compatible with the Eclipse 2021-03 release.
- If a folder was deleted by a host or another participant, it would still remain visible for Eclipse clients. Trying to open a file within this folder would result in the client freezing. Conversely, if a new file was created within a new folder at the client end, both would disappear from the session.
- Installation of CodeTogether would break quick fixes in Eclipse Neon and Photon.
Participants will now see warning markers as well as errors, and quick fixes for warnings will be available too. To head off potential performance issues, we are limiting the number of warnings to 250 per file.
We’ve added syntax coloring for Scala and Dart. Java .class files (if source attached) will be colored as well.
With Eclipse and IntelliJ hosts, clients would often see an incomplete list of quick fix suggestions – this is now fixed.