Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SLVS-1551 Remove the AnalyzerUpdatedForConnection #5775

Conversation

gabriela-trutan-sonarsource
Copy link
Contributor

@gabriela-trutan-sonarsource gabriela-trutan-sonarsource commented Oct 25, 2024

…from IConnectedModeRoslynAnalyzerProvider

The event is not needed, because there is no SlCore listener that informs about the fact that the enterprise analyzer has to be used. Instead it's a service, which SL can use to make a decision.
@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title SLVS-1551 Remove the AnalyzerUpdatedForConnection SLVS-1551 Remove the AnalyzerUpdatedForConnection Oct 25, 2024
Copy link

@georgii-borovinskikh-sonarsource
Copy link
Contributor

If we get rid of this event, there's a race condition between the analyzer choice+registration and the config scope declaration+end of sync (or whenever the data is available for SLCore to tell us which analyzer should be used)

@gabriela-trutan-sonarsource
Copy link
Contributor Author

Closed the PR, because, as discussed with Georgii, we still want the event

@gabriela-trutan-sonarsource gabriela-trutan-sonarsource deleted the gt/cm-roslyn-analyzer-provider-event branch November 5, 2024 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants