As part of its base capability, IntelliJ provides functions for finding and displaying usages of various code elements (e.g. references to a class or method). See IntelliJ's documentation here: https://www.jetbrains.com/help/idea/find-highlight-usages.html. The LSP4iJ plug-in interacts with this subsystem, providing adopters with the ability to extend this base function for their language servers. While LTI does not utilize this directly, LSP4iJ does some things by default which interact with the base function of find usages (particularly for Java files).
There have been two issues resolved in this area in LSP4iJ:
As part of its base capability, IntelliJ provides functions for finding and displaying usages of various code elements (e.g. references to a class or method). See IntelliJ's documentation here: https://www.jetbrains.com/help/idea/find-highlight-usages.html. The LSP4iJ plug-in interacts with this subsystem, providing adopters with the ability to extend this base function for their language servers. While LTI does not utilize this directly, LSP4iJ does some things by default which interact with the base function of find usages (particularly for Java files).
There have been two issues resolved in this area in LSP4iJ:
We should develop tests to ensure that this doesn't regress and continues to work as expected for users of LTI.