Skip to content

refactor(Table): restore dynamic data type check logic#8040

Merged
ArgoZhang merged 5 commits into
mainfrom
feat-table
May 22, 2026
Merged

refactor(Table): restore dynamic data type check logic#8040
ArgoZhang merged 5 commits into
mainfrom
feat-table

Conversation

@ArgoZhang
Copy link
Copy Markdown
Member

@ArgoZhang ArgoZhang commented May 22, 2026

Link issues

fixes #8039

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

Restore dynamic table querying behavior by guarding dynamic queries with type checks and a nullable context.

Bug Fixes:

  • Prevent dynamic table queries from running when a custom query callback is provided or when the row type is not dynamic.
  • Avoid null-reference issues in dynamic querying by handling a nullable dynamic context before accessing items.

Enhancements:

  • Refine dynamic query handling to better respect pagination and selection when using dynamic table data.

Copilot AI review requested due to automatic review settings May 22, 2026 05:12
@bb-auto bb-auto Bot added the enhancement New feature or request label May 22, 2026
@bb-auto bb-auto Bot added this to the v10.6.0 milestone May 22, 2026
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 22, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refactors the table’s dynamic data querying so that dynamic queries are only executed for dynamic item types and safely handles a nullable dynamic context when auto-querying.

File-Level Changes

Change Details Files
Guard dynamic querying logic with null checks and pagination handling when auto-querying dynamic items.
  • Allow the dynamic object context parameter to be nullable in the dynamic query helper method.
  • Only execute dynamic querying, including filter callback and pagination logic, when a non-null dynamic context is provided.
  • Keep pagination calculation and selected row reset behavior unchanged but scoped inside the null-check to avoid null-reference issues.
src/BootstrapBlazor/Components/Table/Table.razor.Toolbar.cs
Restore type-based dynamic data check so dynamic querying runs only for dynamic item types without custom query handlers.
  • Change the condition that triggers dynamic querying to require that no custom OnQueryAsync handler is set.
  • Add a runtime type check ensuring TItem implements IDynamicObject before invoking dynamic querying against the dynamic context.
src/BootstrapBlazor/Components/Table/Table.razor.Edit.cs

Assessment against linked issues

Issue Objective Addressed Explanation
#8039 Restore the dynamic data type check in Table so that dynamic querying is only performed when TItem implements IDynamicObject and no custom OnQueryAsync handler is provided.
#8039 Make querying dynamic items null-safe by allowing a nullable IDynamicObjectContext and guarding uses of it accordingly.

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

Copy link
Copy Markdown
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 - I've left some high level feedback:

  • In QueryDynamicItems, you now null out _rowsCache even when context is null and then do nothing else; consider returning early when context is null to avoid partially changing state in this scenario.
  • The condition in QueryData now guards on OnQueryAsync == null and TItem being IDynamicObject but no longer checks DynamicContext != null; for readability and to keep the control flow explicit, consider including DynamicContext != null in the outer if rather than relying on the inner null-check.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In `QueryDynamicItems`, you now null out `_rowsCache` even when `context` is null and then do nothing else; consider returning early when `context` is null to avoid partially changing state in this scenario.
- The condition in `QueryData` now guards on `OnQueryAsync == null` and `TItem` being `IDynamicObject` but no longer checks `DynamicContext != null`; for readability and to keep the control flow explicit, consider including `DynamicContext != null` in the outer `if` rather than relying on the inner null-check.

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.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the Table component’s “dynamic object” query path to better align with dynamic-type detection by introducing an IDynamicObject type check and making QueryDynamicItems tolerate a nullable dynamic context.

Changes:

  • Update QueryData to use dynamic querying only when OnQueryAsync is not provided and TItem implements IDynamicObject.
  • Update QueryDynamicItems to accept a nullable IDynamicObjectContext and guard against null.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
src/BootstrapBlazor/Components/Table/Table.razor.Toolbar.cs Makes QueryDynamicItems accept nullable context and wraps dynamic query logic in a null check.
src/BootstrapBlazor/Components/Table/Table.razor.Edit.cs Changes the condition that selects the dynamic-query path in QueryData.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


if (DynamicContext != null)

if (OnQueryAsync == null && typeof(TItem).IsAssignableTo(typeof(IDynamicObject)))
Comment on lines +1240 to 1246
private void QueryDynamicItems(QueryPageOptions queryOption, IDynamicObjectContext? context, bool isAutoQuery = true)
{
if (isAutoQuery)
{
_rowsCache = null;
var items = context.GetItems();
if (context.OnFilterCallback != null)
if (context != null)
{
@codecov
Copy link
Copy Markdown

codecov Bot commented May 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (03f2385) to head (c67438e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #8040   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          766       766           
  Lines        34154     34157    +3     
  Branches      4696      4697    +1     
=========================================
+ Hits         34154     34157    +3     
Flag Coverage Δ
BB 100.00% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ArgoZhang ArgoZhang merged commit 0c81f10 into main May 22, 2026
4 checks passed
@ArgoZhang ArgoZhang deleted the feat-table branch May 22, 2026 05:47
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.

refactor(Table): restore dynamic data type check logic

2 participants