Skip to content

Conversation

@ArgoZhang
Copy link
Member

@ArgoZhang ArgoZhang commented Mar 26, 2025

Link issues

fixes #5685

Summary By Copilot

This pull request includes several changes to the Table component in the BootstrapBlazor library. The main focus is on renaming the VirtualizeElement field to _virtualizeElement and ensuring it is properly referenced throughout the codebase.

Changes to Table component:

Test updates:

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

Modify the Table component to improve virtualization handling and add null checking for the virtualize element

Bug Fixes:

  • Prevent potential null reference issues with the virtualization element in the Table component

Enhancements:

  • Rename VirtualizeElement to _virtualizeElement with added null checking
  • Update reflection and reference handling for the virtualize element

Tests:

  • Update test method to use reflection for accessing the private virtualize element

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Mar 26, 2025

Reviewer's Guide by Sourcery

This pull request renames the VirtualizeElement field to _virtualizeElement in the Table component and updates all references to this field throughout the codebase. This includes changes in the Table.razor, Table.razor.Edit.cs, Table.razor.cs, and TableTest.cs files.

Sequence diagram for RefreshDataAsync call in Virtual ScrollMode

sequenceDiagram
    participant Table
    participant Virtualize

    Table->>Virtualize: RefreshDataAsync()
    Virtualize-->>Table: Task
Loading

Updated class diagram for the Table component

classDiagram
  class Table~TItem~ {
    -Virtualize~TItem~? VirtualizeElement
    +Virtualize~TItem~? _virtualizeElement
  }
  note for Table~TItem~ "VirtualizeElement field renamed to _virtualizeElement and made private with [NotNull] attribute"
Loading

File-Level Changes

Change Details Files
Renamed VirtualizeElement field to _virtualizeElement and updated its references.
  • Renamed VirtualizeElement to _virtualizeElement.
  • Updated the Virtualize component reference to use _virtualizeElement.
  • Updated the OnClickCardView method to use _virtualizeElement.
  • Updated the TestLoopQueryAsync method to use _virtualizeElement.
src/BootstrapBlazor/Components/Table/Table.razor
test/UnitTest/Components/TableTest.cs
src/BootstrapBlazor/Components/Table/Table.razor.Edit.cs
src/BootstrapBlazor/Components/Table/Table.razor.cs

Assessment against linked issues

Issue Objective Addressed Explanation
#5685 Fix the bug where OnTreeExpand is not triggered when ScrollMode is set to Virtual in version 9.4.10. The PR focuses on renaming VirtualizeElement to _virtualizeElement and updating references, but it does not address the core issue of OnTreeExpand not triggering with virtual scrolling enabled.
#5685 Ensure that the Tree mode of the Table component supports virtual scrolling. The PR does not implement virtual scrolling support for the Tree mode. It only refactors the VirtualizeElement field.

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!
  • 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

@bb-auto bb-auto bot added the enhancement New feature or request label Mar 26, 2025
@bb-auto bb-auto bot added this to the v9.4.0 milestone Mar 26, 2025
@ArgoZhang ArgoZhang merged commit f99ad91 into main Mar 26, 2025
3 checks passed
@ArgoZhang ArgoZhang deleted the fix-table branch March 26, 2025 10:31
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:

Overall Comments:

  • Consider using nameof when referring to the private field _virtualizeElement in the test to avoid hardcoding the string.
Here's what I looked at during the review
  • 🟡 General issues: 1 issue found
  • 🟢 Security: all looks good
  • 🟡 Testing: 1 issue found
  • 🟢 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.

/// <summary>
/// 获得/设置 内置虚拟化组件实例
/// </summary>
protected Virtualize<TItem>? VirtualizeElement { get; set; }
Copy link
Contributor

Choose a reason for hiding this comment

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

question (bug_risk): Using [NotNull] with conditional assignment may be misleading.

The _virtualizeElement field is marked with [NotNull] yet may remain null depending on the rendering branch. Please verify that this attribute accurately reflects its lifecycle or consider handling the nullability to avoid potential warnings or runtime issues.

Comment on lines +8914 to +8915
var fieldInfo = GetType().BaseType!.GetField("_virtualizeElement", BindingFlags.NonPublic | BindingFlags.Instance)!;
if (ScrollMode == ScrollMode.Virtual && fieldInfo.GetValue(this) is Virtualize<Foo> element)
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion (testing): Avoid testing private fields with reflection.

Testing private fields using reflection makes tests brittle and tightly coupled to implementation details. Consider exposing the necessary information through a protected property or method if it's essential for testing. Alternatively, refactor the test to interact with the component's public API and verify the expected behavior without relying on internal state.

Suggested implementation:

            if (ScrollMode == ScrollMode.Virtual && VirtualizeElement is Virtualize<Foo> element)

Ensure that the component exposes a protected property VirtualizeElement (if not already present) that returns the value of the private _virtualizeElement field. For example, in the component's base class you may add:

protected Virtualize? VirtualizeElement => _virtualizeElement;

This change avoids testing private fields via reflection and makes the test less brittle while still exposing the necessary state for verifying the component behavior.

@codecov
Copy link

codecov bot commented Mar 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

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

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #5721   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          657       657           
  Lines        29830     29829    -1     
  Branches      4229      4229           
=========================================
- Hits         29830     29829    -1     

☔ 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.

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(Table): Tree 模式支持虚拟滚动

2 participants