chore(ErroLogger): add navigation url info

[ArgoZhang]

add navigation url info

Summary of the changes (Less than 80 chars)

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

Description

fixes #5261

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:

• Fix issue chore(ErroLogger): add navigation url info #5261 by adding the current URL to the error logs.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds the current navigation URL to the error logs generated by the BootstrapBlazorErrorBoundary component.

Sequence diagram for error logging with navigation URL

sequenceDiagram
    participant User
    participant ErrorBoundary as BootstrapBlazorErrorBoundary
    participant ToastService
    participant Logger
    participant NavigationManager

    User->>ErrorBoundary: Triggers error
    ErrorBoundary->>ToastService: Display error toast
    ErrorBoundary->>NavigationManager: Get current URL
    ErrorBoundary->>Logger: Log error with URL info

Loading

File-Level Changes

Change	Details	Files
Added the navigation URL to the error logs.	Injected the NavigationManager service. Modified the error logging message to include the current NavigationManager.Uri.	src/BootstrapBlazor/Components/ErrorLogger/BootstrapBlazorErrorBoundary.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5261	Add navigation URL information to the error logging	✅

Possibly linked issues

• chore(ErroLogger): add navigation url info #5261: The PR fixes issue chore(ErroLogger): add navigation url info #5261 by adding navigation URL information to the error logger, which helps in identifying the location of the error.
• chore(ErroLogger): add navigation url info #5261: The PR adds navigation url info to the ErrorLogger, which is exactly what the issue describes.
• chore(ErroLogger): add navigation url info #5261: The PR fixes the pagination bug by adding navigation URL info to error logging, allowing the source of the redirect to be identified.

---

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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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 - here's some feedback:

Overall Comments:

• Please complete the PR template fully, including risk assessment, verification steps, and self-check items. This helps maintain project quality and documentation standards.

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 (e1f1352) to head (c05c6af).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5262   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          639       639           
  Lines        28756     28757    +1     
  Branches      4085      4085           
=========================================
+ Hits         28756     28757    +1     

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