feat(Table): add OverscanCount parameter

[ArgoZhang]

Link issues

fixes #5729

Summary By Copilot

This pull request includes several changes to the BootstrapBlazor project, focusing on improving the table component's functionality and fixing a minor typo in the localization file. The most important changes include adding a new parameter for virtual scrolling, updating the table component to use this parameter, and making minor code improvements.

Enhancements to the table component:

• src/BootstrapBlazor/Components/Table/Table.razor: Updated the Virtualize component to use the new OverscanCount parameter for better control over virtual scrolling.
• src/BootstrapBlazor/Components/Table/Table.razor.cs: Introduced a new OverscanCount parameter with a default value of 10, which allows users to set the overscan count for virtual scrolling.
• test/UnitTest/Components/TableTest.cs: Added a test case to ensure the OverscanCount parameter is correctly set and used in the table component.

Minor code improvements:

• src/BootstrapBlazor/Components/Table/Table.razor.TreeNode.cs: Removed unnecessary [NotNull] attribute from the TreeRows property and added a missing newline for better code readability. [1] [2]

Localization fix:

• src/BootstrapBlazor.Server/Locales/en-US.json: Corrected a typo by changing "UniverIcons" to "UniverIcon".

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

Add OverscanCount parameter to improve virtual scrolling control in the Table component

New Features:

• Introduced a new OverscanCount parameter for the Table component to provide more granular control over virtual scrolling

Bug Fixes:

• Corrected a typo in the en-US localization file

Enhancements:

• Updated Table component to use the new OverscanCount parameter with a default value of 10
• Improved code readability by removing unnecessary attributes and adding missing newlines

Tests:

• Added a test case to verify the OverscanCount parameter functionality in the Table component

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces the OverscanCount parameter to the Table component, allowing users to configure the number of off-screen rows to render in virtual scrolling mode. It also includes minor code improvements and a typo fix in the localization file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Introduced a new OverscanCount parameter to the Table component for configuring the number of off-screen rows to render in virtual scrolling mode.	Added OverscanCount parameter with a default value of 10. Updated the Virtualize component to use the OverscanCount parameter. Added a test case to verify the functionality of the OverscanCount parameter.	src/BootstrapBlazor/Components/Table/Table.razor.cs src/BootstrapBlazor/Components/Table/Table.razor test/UnitTest/Components/TableTest.cs
Made minor improvements to the Table component's TreeNode class.	Removed unnecessary [NotNull] attribute from the TreeRows property. Added a missing newline for better code readability.	src/BootstrapBlazor/Components/Table/Table.razor.TreeNode.cs
Fixed a typo in the English localization file.	Corrected "UniverIcons" to "UniverIcon".	src/BootstrapBlazor.Server/Locales/en-US.json

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5729	Add an OverscanCount parameter to the Table component to control the number of off-screen rows rendered in virtual scrolling mode.	✅

Possibly linked issues

• feat(Table): add OverscanCount parameter #5729: The PR fixes the styling issue by adding a new OverscanCount parameter to control virtual scrolling behavior.

---

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:

• Consider adding a range check to the OverscanCount parameter to prevent unexpected behavior with very large or negative values.
• Good job including a unit test for the new OverscanCount parameter.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 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 ✨

• 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 (da29238) to head (83c8808).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5730   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          657       657           
  Lines        29832     29833    +1     
  Branches      4230      4230           
=========================================
+ Hits         29832     29833    +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.