Skip to content

Conversation

@ArgoZhang
Copy link
Member

@ArgoZhang ArgoZhang commented Jun 4, 2025

Link issues

fixes #6151

Summary By Copilot

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

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

Support showing only exception messages in release mode by injecting IHostEnvironment into the error boundary, refactoring the error-handling flow, and updating handler implementations to async for full details in development and minimal messaging in production

New Features:

  • Support release-mode only showing exception message toast

Enhancements:

  • Inject IHostEnvironment into error boundary to distinguish development and production behavior
  • Refactor OnErrorAsync to always log errors and extract toast logic to a new ShowErrorToast method
  • Modify RenderException to call OnErrorAsync then display full exception details in development via handler or show only toast message in non-development environments
  • Convert HandlerException implementations in TabItemContent, Layout, and ModalDialog to async Task with await

@bb-auto bb-auto bot added the enhancement New feature or request label Jun 4, 2025
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jun 4, 2025

Reviewer's Guide

This PR enhances the error logging component to display only exception messages in non-development environments by injecting the host environment, refactoring the error handling flow (OnErrorAsync and RenderException), introducing an environment check for toast notifications, and standardizing async HandlerException methods across components.

Sequence Diagram: RenderException with Handler in Development Mode

sequenceDiagram
    participant Caller
    participant BEB as BootstrapBlazorErrorBoundary
    participant Logger
    participant Env as IHostEnvironment
    participant H as "handler (IHandlerException)"

    Caller->>BEB: RenderException(exception, handler)
    BEB->>BEB: OnErrorAsync(exception)
    activate BEB
    BEB->>Logger: LogError(exception, "Error details...")
    deactivate BEB
    BEB->>Env: IsDevelopment()
    Env-->>BEB: true
    BEB->>H: HandlerException(exception, ExceptionContent)
Loading

Sequence Diagram: RenderException with Handler in Non-Development Mode

sequenceDiagram
    participant Caller
    participant BEB as BootstrapBlazorErrorBoundary
    participant Logger
    participant Env as IHostEnvironment
    participant TS as ToastService

    Caller->>BEB: RenderException(exception, handler)
    BEB->>BEB: OnErrorAsync(exception)
    activate BEB
    BEB->>Logger: LogError(exception, "Error details...")
    deactivate BEB
    BEB->>Env: IsDevelopment()
    Env-->>BEB: false
    BEB->>TS: Error(ToastTitle, exception.Message)
Loading

Updated Class Diagram for BootstrapBlazorErrorBoundary

classDiagram
    class BootstrapBlazorErrorBoundary {
        -IHostEnvironment IHostEnvironment
        #OnErrorAsync(Exception exception) Task
        +RenderException(Exception exception, IHandlerException? handler) Task
        -ShowErrorToast(Exception exception) Task
    }
    BootstrapBlazorErrorBoundary --|> ErrorBoundaryBase
    BootstrapBlazorErrorBoundary ..> IHostEnvironment : uses
    BootstrapBlazorErrorBoundary ..> IHandlerException : uses
    BootstrapBlazorErrorBoundary ..> ToastService : uses
    BootstrapBlazorErrorBoundary ..> ILogger : uses
Loading

File-Level Changes

Change Details Files
Inject and utilize IHostEnvironment for environment-specific error handling
  • Added IHostEnvironment injection property to ErrorBoundary
  • Wrapped IHandlerException invocation and toast display in environment check
src/BootstrapBlazor/Components/ErrorLogger/BootstrapBlazorErrorBoundary.cs
Refactor OnErrorAsync to remove direct toast calls and return completed tasks
  • Removed ShowToast logic from OnErrorAsync
  • Changed async signature to return Task.CompletedTask
src/BootstrapBlazor/Components/ErrorLogger/BootstrapBlazorErrorBoundary.cs
Overhaul RenderException flow for release vs development modes
  • Moved initial log call into RenderException before handler logic
  • In development mode, invoke handler.HandlerException; otherwise show toast
  • Introduced ShowErrorToast helper method for conditional toast display
src/BootstrapBlazor/Components/ErrorLogger/BootstrapBlazorErrorBoundary.cs
Standardize HandlerException methods to asynchronous with inheritdoc
  • Changed HandlerException in TabItemContent to async/await
  • Updated HandlerException docs to use inheritdoc in Layout and ModalDialog
src/BootstrapBlazor/Components/Tab/TabItemContent.cs
src/BootstrapBlazor/Components/Layout/Layout.razor.cs
src/BootstrapBlazor/Components/Modal/ModalDialog.razor.cs

Assessment against linked issues

Issue Objective Addressed Explanation
#6151 Only show exception messages in Release mode.

Possibly linked issues


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!

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

@bb-auto bb-auto bot added this to the 9.7.0 milestone Jun 4, 2025
sourcery-ai[bot]
sourcery-ai bot previously approved these changes Jun 4, 2025
Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @ArgoZhang - I've reviewed your changes - here's some feedback:

  • Rename the injected IHostEnvironment property to HostEnvironment (or a similar non-interface-prefixed name) to avoid confusion.
  • Refactor the repeated ToastService.Error and environment-check logic into a shared helper to reduce duplication.
  • For methods that only await and return a single Task (e.g. HandlerException), consider removing the async keyword and returning the Task directly.
Here's what I looked at during the review
  • 🟡 General issues: 2 issues found
  • 🟢 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 ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@codecov
Copy link

codecov bot commented Jun 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4640cae) to head (d9f4db9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #6152   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          703       703           
  Lines        31108     31119   +11     
  Branches      4398      4399    +1     
=========================================
+ Hits         31108     31119   +11     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ArgoZhang ArgoZhang merged commit 8b47783 into main Jun 4, 2025
3 checks passed
@ArgoZhang ArgoZhang deleted the refactor-error branch June 4, 2025 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(IErrorLogger): support Release mode only show exception message

2 participants