Adding analyzer to warn about JSInterop calls not wrapped in a try catch block

[MayaKirova]

Adding analyzer to warn about JSInterop calls not wrapped in a try catch block

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Description

Added analyzer that shows warnning and code fixer that wraps the JSInterop calls (InvokeAsync, InvokeVoidAsync etc.) in try/catch block.

Also added some tests:

Area	Test Scenario	Expected Result
Analyzer	Unguarded IJSRuntime extension call (InvokeVoidAsync)	Warning is reported
Analyzer	Unguarded IJSObjectReference extension call (InvokeVoidAsync)	Warning is reported
Analyzer	Unguarded IJSRuntime.InvokeAsync<T> call	Warning is reported
Analyzer	Unguarded IJSObjectReference.InvokeAsync<T> call	Warning is reported
Analyzer	Unguarded IJSInProcessRuntime.Invoke<T> call	Warning is reported
Analyzer	Unguarded IJSInProcessObjectReference.Invoke<T> call	Warning is reported
Analyzer	JS interop call already inside try/catch	No diagnostic is reported
Analyzer	JS interop call nested in guarded flow (if inside try/catch)	No diagnostic is reported
Code Fixer	Unguarded awaited InvokeVoidAsync	Call is wrapped in try/catch
Code Fixer	Unguarded awaited InvokeAsync<T>	Call is wrapped in try/catch
Code Fixer	Unguarded non-awaited InvokeVoidAsync	Call is wrapped in try/catch

Fixes #67306

[dotnet-policy-service]

Thanks for your PR, @MayaKirova. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[Copilot]

Pull request overview

Adds a new Components analyzer/code fix intended to warn on unguarded JS interop calls and offer an automatic “wrap in try/catch” fix, with accompanying unit tests and localized resources.

Changes:

• Introduces JSInteropAnalyzer to report a warning for JS interop invocations not inside a try/catch.
• Adds JSInteropCodeFixProvider to wrap the targeted invocation in a try/catch block.
• Adds analyzer/code-fix tests plus new diagnostic descriptor + resource strings.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
src/Components/Analyzers/src/JSInteropAnalyzer.cs	New analyzer for detecting unguarded JS interop calls.
src/Components/Analyzers/src/JSInteropCodeFixProvider.cs	New code fix provider to wrap calls in try/catch.
src/Components/Analyzers/src/DiagnosticDescriptors.cs	Adds BL0015 descriptor for the new analyzer.
src/Components/Analyzers/src/Resources.resx	Adds localized strings for the new diagnostic and fix title.
src/Components/Analyzers/test/JSInteropAnalyzerTest.cs	New tests validating diagnostics are reported/suppressed appropriately.
src/Components/Analyzers/test/JSInteropCodeFixProviderTest.cs	New tests validating the code fix output.

[ilonatommy]

Fast pass without the fixer.

[oroztocil]

There are additional interop methods on these interfaces since .NET 10 (e.g., IJSRuntime.GetValueAsync). They should probably be covered by the analyzer as well, since they have the same risks.

[MayaKirova]

There are additional interop methods on these interfaces since .NET 10 (e.g., IJSRuntime.GetValueAsync). They should probably be covered by the analyzer as well, since they have the same risks.

@oroztocil

Those are covered I believe. I also added some tests: ff91d9e

Let me know if I'm missing anything else. :)

[ilonatommy]

An idea for simplification, not tested

[ilonatommy]

/ba-g failures not connected