Skip to content

doc(Table): update documentation for Table search function#7792

Merged
ArgoZhang merged 2 commits intomainfrom
feat-search
Mar 24, 2026
Merged

doc(Table): update documentation for Table search function#7792
ArgoZhang merged 2 commits intomainfrom
feat-search

Conversation

@ArgoZhang
Copy link
Copy Markdown
Member

@ArgoZhang ArgoZhang commented Mar 24, 2026

Link issues

fixes #7791

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

Update Table search demo documentation to better explain the search form behavior and warnings.

Documentation:

  • Add detailed bullet-point description of the Table search form usage in the demo.
  • Document warning tips for configuring and using the Table search form, localized for supported languages.

Copilot AI review requested due to automatic review settings March 24, 2026 03:53
@bb-auto bb-auto bot added the documentation Improvements or additions to documentation label Mar 24, 2026
@bb-auto bb-auto bot added this to the v10.4.0 milestone Mar 24, 2026
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai bot commented Mar 24, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Table search sample documentation by expanding the description of the search form, adding a warning tip section, and localizing the new text in both English and Chinese locale files.

File-Level Changes

Change Details Files
Enhance the Table search sample page with more detailed search form documentation and a warning tip.
  • Extend the search form description section with a bulleted list rendered via localized markup strings.
  • Add a Tips component below the first demo block to display warning guidance text using localization.
src/BootstrapBlazor.Server/Components/Samples/Table/TablesSearch.razor
Add localization entries for the new search form description items and warning tips in both English and Chinese.
  • Introduce new keys for additional search form description list items in the English locale JSON.
  • Introduce a new key for search form warning tips text in the English locale JSON.
  • Mirror the new description and warning tip keys in the Chinese locale JSON with appropriate translations or placeholders.
src/BootstrapBlazor.Server/Locales/en-US.json
src/BootstrapBlazor.Server/Locales/zh-CN.json

Assessment against linked issues

Issue Objective Addressed Explanation
#7791 Update the documentation/sample for the Table search function to provide clearer descriptive text and tips (including any necessary localization entries).

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:

  • The new localized strings rendered via MarkupString (e.g., SearchFormDescItem1/2, SearchFormWarningTips) assume trusted HTML, so ensure these values are strictly controlled and not built from any user input to avoid XSS issues.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new localized strings rendered via `MarkupString` (e.g., `SearchFormDescItem1/2`, `SearchFormWarningTips`) assume trusted HTML, so ensure these values are strictly controlled and not built from any user input to avoid XSS issues.

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.

@ArgoZhang ArgoZhang merged commit 8b00dd1 into main Mar 24, 2026
6 checks passed
@ArgoZhang ArgoZhang deleted the feat-search branch March 24, 2026 03:55
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

Updates the Table search documentation sample to better explain UseSearchForm behavior and customization options, addressing issue #7791.

Changes:

  • Refines the SearchForm description by splitting customization guidance into bullet items.
  • Adds a warning tip recommending UseSearchForm (post v10.4.2) over older search examples.
  • Updates both zh-CN and en-US localization resources to support the new documentation content.

Reviewed changes

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

File Description
src/BootstrapBlazor.Server/Locales/zh-CN.json Splits SearchForm description into multiple items and adds a new warning tip string (zh-CN).
src/BootstrapBlazor.Server/Locales/en-US.json Adds new SearchForm description list items and a warning tip string (en-US).
src/BootstrapBlazor.Server/Components/Samples/Table/TablesSearch.razor Renders the new localized bullet list under SearchForm and adds a new warning <Tips> block before older examples.

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

@@ -5065,9 +5065,12 @@
"EditModelTitle": "Edit Test Data Window",
"NamePlaceholder": "Please enter your name within 50 characters",
"SearchFormDesc": "When <code>UseSearchForm</code> is enabled and <code>SearchItems</code> is not provided, it will default to using <code>TableColumn</code> with <code>Searchable=\"true\"</code>. You can customize the metadata through the <code>SearchFormItemMetadata</code> property in <code>TableColumn</code>",
Copy link

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

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

SearchFormDesc still contains the “customize metadata … SearchFormItemMetadata” sentence, but that same information is now repeated in the new bullet item SearchFormDescItem1. This makes the English docs redundant and inconsistent with zh-CN (which moved the customization details into list items). Consider shortening SearchFormDesc to only explain the default behavior, and keep customization guidance exclusively in the list items.

Suggested change
"SearchFormDesc": "When <code>UseSearchForm</code> is enabled and <code>SearchItems</code> is not provided, it will default to using <code>TableColumn</code> with <code>Searchable=\"true\"</code>. You can customize the metadata through the <code>SearchFormItemMetadata</code> property in <code>TableColumn</code>",
"SearchFormDesc": "When <code>UseSearchForm</code> is enabled and <code>SearchItems</code> is not provided, it will default to using <code>TableColumn</code> with <code>Searchable=\"true\"</code>.",

Copilot uses AI. Check for mistakes.
"SearchFormIntro": "通过设置 <code>UseSearchForm=\"true\"</code> 开启搜索表单功能,通过 <code>SearchItems</code> 配置搜索表单内搜索项,适用于自定义复杂搜索条件的场景",
"SearchFormTips": "开启 <code>UseSearchForm</code> 后 <code>SearchModel</code> <code>SearchTemplate</code> <code>CustomerSearchModel</code> <code>CustomerSearchTemplate</code> 均不生效",
"SearchFormTitle": "搜索表单",
"SearchFormWarningTips": "<code>BootstrapBlazor</code> v10.4.2 版本后增加 <code>UseSearchForm</code> 参数后以下示例均可以不学习了,强烈推荐使用 <code>UseSearchForm</code>",
Copy link

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

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

The zh-CN text for SearchFormWarningTips has a grammatical duplication (“版本后增加 … 参数后 …”), and the wording “不学习了” is ambiguous/colloquial for documentation. Consider rephrasing to remove the duplicated “后” and use clearer wording (e.g., “自 v10.4.2 起新增…,以下示例可作为旧方案参考/可忽略…”) while keeping the intended meaning.

Suggested change
"SearchFormWarningTips": "<code>BootstrapBlazor</code> v10.4.2 版本后增加 <code>UseSearchForm</code> 参数后以下示例均可以不学习了,强烈推荐使用 <code>UseSearchForm</code>",
"SearchFormWarningTips": "<code>BootstrapBlazor</code> v10.4.2 起新增 <code>UseSearchForm</code> 参数,以下示例可作为旧方案参考,推荐优先使用 <code>UseSearchForm</code>",

Copilot uses AI. Check for mistakes.
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 24, 2026

Codecov Report

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

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #7792   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          764       764           
  Lines        34109     34109           
  Branches      4697      4697           
=========================================
  Hits         34109     34109           
Flag Coverage Δ
BB 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

doc(Table): update documentation for Table search function

2 participants