Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Split up the DiagnosticCollections per tool type #2109

Merged

Conversation

segevfiner
Copy link
Contributor

This code seems quite sensitive, this needs a careful review & some testing. Please pay extra attention to the diagnostic de-duping code in handleDiagnosticErrors.

Fixes #2100, fixes #2101

Copy link
Contributor

@ramya-rao-a ramya-rao-a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good @segevfiner

I have pushed a commit to refactor the de-dupe logic in handleDiagnosticErrors, do take a look.

Copy link
Contributor Author

@segevfiner segevfiner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have pushed a commit to refactor the de-dupe logic in handleDiagnosticErrors, do take a look.

I actually thought about doing that myself when touching that code. 😊 Seems to be working fine.

});
}

function deDupeDiagnostics(buildDiagnostics: vscode.Diagnostic[], otherDiagnostics: vscode.Diagnostic[]): vscode.Diagnostic[] {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function is really more generic than just for the buildDiagnostics. Might be a bit hard to come up with good "generic" names for the parameters though 😛

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants