fix(Table): use request.Count parameter on virtualize mode

[densen2014]

ScrollModeVirtual paging numbers Inaccurate when search conditions change

Issue

fixes #5085

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 a bug where changing search conditions caused inaccurate paging numbers in tables using ScrollModeVirtual.

[bb-auto]

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

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request fixes a bug in the Table component where the paging numbers were inaccurate when search conditions changed. The fix involves updating the LoadItems method to use the original page size when search conditions are present. This ensures that the correct number of items are displayed on each page, regardless of the search criteria.

Sequence diagram for Table LoadItems with Search Conditions

sequenceDiagram
    participant User
    participant Table
    participant ItemsProvider

    User->>Table: Change Search Conditions
    Table->>ItemsProvider: LoadItems(request)
    Note over ItemsProvider: Check if SearchText exists
    alt SearchText not empty and TotalCount > 0
        ItemsProvider->>ItemsProvider: Calculate pageItems using TotalCount
    else
        ItemsProvider->>ItemsProvider: Use request.Count as pageItems
    end
    ItemsProvider->>ItemsProvider: QueryData()
    ItemsProvider-->>Table: Return ItemsProviderResult
    Table-->>User: Display Updated Results

Loading

File-Level Changes

Change	Details	Files
Updated the paging logic to handle search conditions correctly.	Modified the LoadItems method to use the original page size when search conditions are present. This ensures that the correct number of items are displayed on each page when searching. Added a conditional check for search text within the calculation of _pageItems to determine whether to use the original request count or a count based on the total count and start index. The change ensures that the number of items displayed per page remains consistent, even when the total count changes due to filtering. This prevents issues where the last page might appear empty or incomplete when search criteria are applied and the total count is reduced as a result of filtering.	src/BootstrapBlazor/Components/Table/Table.razor.cs

---

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 @densen2014 - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please complete the PR template properly, especially the risk assessment and verification sections. This helps reviewers better understand the impact and testing done for this pagination-related change.

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

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5089   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          632       632           
  Lines        28096     28096           
  Branches      4035      4034    -1     
=========================================
  Hits         28096     28096           

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