Currently it's possible to trigger multiple analyses of the same file when no changes are present. I'd suggest checking the file's SHA-1 hash before starting an analysis to determine whetever the content has actually changed.
Alongside this. I'd also suggest canceling any in-progress analysis if the user saves again shortly after (and a change is present), so only the latest version is analyzed. This would prevent redundant duplicate analyses and avoid wasting resources.
Currently it's possible to trigger multiple analyses of the same file when no changes are present. I'd suggest checking the file's SHA-1 hash before starting an analysis to determine whetever the content has actually changed.
Alongside this. I'd also suggest canceling any in-progress analysis if the user saves again shortly after (and a change is present), so only the latest version is analyzed. This would prevent redundant duplicate analyses and avoid wasting resources.