refactor(LoadModule): add logger information for load module failed

[ArgoZhang]

add logger information for load module failed

Summary of the changes (Less than 80 chars)

简单描述你更改了什么, 不超过80个字符；如果有关联 Issue 请在下方填写相关编号

Description

fixes #5147

Regression?

• Yes
• No

[If yes, specify the version the behavior has regressed from]

[是否影响老版本]

Risk

• High
• Medium
• Low

[Justify the selection above]

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Bug Fixes:

• Fixed an issue where module load failures were not logged.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds logging for when loading a JS module fails, which helps with debugging. It also adds a version parameter to the LoadUtility method.

Sequence diagram for JS module loading with error handling

sequenceDiagram
    participant App
    participant JSRuntime
    participant JSModule
    participant Console

    App->>JSRuntime: LoadModule(fileName, version)
    JSRuntime->>JSModule: Import JS Module
    alt Module Load Failed
        JSModule-->>Console: Log error message
        Note right of Console: New: Added logging for<br/>module load failures
        JSModule-->>App: Throw JSException
    else Module Load Success
        JSModule-->>App: Return JSModule instance
    end

Loading

Class diagram for JSModule and extensions

classDiagram
    class JSModule {
        -IJSObjectReference jSObjectReference
        +InvokeVoidAsync(string identifier, CancellationToken cancellationToken, params object?[]? args)
        +InvokeAsync<TValue>(string identifier, CancellationToken cancellationToken, params object?[]? args)
    }

    class JSModuleExtensions {
        +LoadUtility(IJSRuntime jsRuntime, string? version)*
        +LoadModule(IJSRuntime jsRuntime, string fileName, string? version)*
    }
    note for JSModuleExtensions "Modified: Added version parameter
and enhanced error logging"

Loading

File-Level Changes

Change	Details	Files
Added logging for JS module loading failures.	Added try-catch blocks to the InvokeVoidAsync and InvokeAsync methods to catch JSExceptions. Added a console log message when a JSException is caught in debug mode. Added a console log message when a JSException is caught in the LoadModule method in debug mode.	src/BootstrapBlazor/Utils/JSModule.cs src/BootstrapBlazor/Extensions/JSModuleExtensions.cs
Added a version parameter to the LoadUtility method.	Added an optional string parameter named version to the LoadUtility method. The LoadUtility method now calls the LoadModule method with the provided version.	src/BootstrapBlazor/Extensions/JSModuleExtensions.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5147	Add logger information for load module failed scenarios	✅

Possibly linked issues

• refactor(LoadModule): add logger information for load module failed #5147: The PR addresses the issue by adding logging for load module failures.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ArgoZhang - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (3279623) to head (7c62987).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5148   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          634       634           
  Lines        28196     28191    -5     
  Branches      4038      4038           
=========================================
- Hits         28196     28191    -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.