[optimization] avoid writing spring index cache twice on didSave event #1143
Labels
for: eclipse
something that is specific for Eclipse
for: vscode
something that is specific for VSCode
theme: performance
type: enhancement
Milestone
If the client sends a didSave event as well as a fileUpdated event, the Spring indexer for Java files writes the cache twice, even though It checks whether certain files have been changed since the last cache update.
The text was updated successfully, but these errors were encountered: