Skip to content

doc(NavMenu): update component category#8138

Merged
ArgoZhang merged 3 commits into
mainfrom
doc-local
Jun 21, 2026
Merged

doc(NavMenu): update component category#8138
ArgoZhang merged 3 commits into
mainfrom
doc-local

Conversation

@ArgoZhang

@ArgoZhang ArgoZhang commented Jun 21, 2026

Copy link
Copy Markdown
Member

Link issues

fixes #8137

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

Enhancements:

  • Rename NavMenu item labels to use more specific Bootstrap/Console-related localization keys across English and Chinese locales.

@bb-auto bb-auto Bot added the documentation Improvements or additions to documentation label Jun 21, 2026
@bb-auto bb-auto Bot added this to the v10.7.0 milestone Jun 21, 2026
@sourcery-ai

sourcery-ai Bot commented Jun 21, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates several NavMenu item labels to use more specific localization keys for Bootstrap-based components and aligns the corresponding English and Chinese locale entries with the new key names.

Sequence diagram for NavMenu localization key updates

sequenceDiagram
    actor User
    participant NavMenu
    participant MenusLocalizerExtensions
    participant Localizer

    User ->> NavMenu: render
    NavMenu ->> MenusLocalizerExtensions: AddForm(item)
    MenusLocalizerExtensions ->> Localizer: this[string key=BootstrapInput]
    Localizer -->> MenusLocalizerExtensions: localizedText
    MenusLocalizerExtensions ->> NavMenu: set DemoMenuItem.Text

    NavMenu ->> MenusLocalizerExtensions: AddQuickStar(item)
    MenusLocalizerExtensions ->> Localizer: this[string key=BootstrapLabel]
    Localizer -->> MenusLocalizerExtensions: localizedText
    MenusLocalizerExtensions ->> NavMenu: set DemoMenuItem.Text

    NavMenu ->> MenusLocalizerExtensions: AddData(item)
    MenusLocalizerExtensions ->> Localizer: this[string key=BootstrapBlazorIcon]
    Localizer -->> MenusLocalizerExtensions: localizedText
    MenusLocalizerExtensions ->> NavMenu: set DemoMenuItem.Text
Loading

File-Level Changes

Change Details Files
Update NavMenu demo items to use more specific localization keys for Bootstrap-related components.
  • Change the 'Labels' menu item to use the 'BootstrapLabel' localization key while retaining the same route.
  • Update input-related menu items to use 'BootstrapInput', 'BootstrapInputNumber', and 'BootstrapInputGroup' localization keys instead of the more generic ones.
  • Rename the IP-related menu item localization key from 'Ip' to 'IpAddress'.
  • Change the icon demo menu item to use the 'BootstrapBlazorIcon' localization key.
  • Change the console demo menu item to use the 'ConsoleLogger' localization key.
src/BootstrapBlazor.Server/Extensions/MenusLocalizerExtensions.cs
Align English and Chinese locale resource files with new NavMenu localization key names.
  • Add or rename locale entries for 'BootstrapLabel', 'BootstrapInput', 'BootstrapInputNumber', 'BootstrapInputGroup', 'IpAddress', 'BootstrapBlazorIcon', and 'ConsoleLogger' in the English locale.
  • Add or rename the corresponding Chinese locale entries to match the new key names.
src/BootstrapBlazor.Server/Locales/en-US.json
src/BootstrapBlazor.Server/Locales/zh-CN.json

Assessment against linked issues

Issue Objective Addressed Explanation
#8137 Update the NavMenu documentation/menu entries to use the new component category names for the affected components (e.g., Label, Input, InputNumber, InputGroup, Ip, Icon, Console).

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


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.

@bb-auto bb-auto Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Auto approved by bb-auto

@ArgoZhang ArgoZhang merged commit 05ee26e into main Jun 21, 2026
5 checks passed
@ArgoZhang ArgoZhang deleted the doc-local branch June 21, 2026 07:05
@codecov

codecov Bot commented Jun 21, 2026

Copy link
Copy Markdown

Codecov Report

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

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #8138   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          766       766           
  Lines        34213     34213           
  Branches      4696      4696           
=========================================
  Hits         34213     34213           
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 Harness.
📢 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(NavMenu): update component category

1 participant