feat(Stack): rename bb_stack to bb-stack

[ArgoZhang]

Link issues

fixes #6188

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

Rename Stack component CSS classes from snake_case to kebab-case and update related styles, class builders, and tests accordingly

Enhancements:

• Use kebab-case class names (bb-stack, bb-stack-item) in Stack component rendering logic
• Update sample CSS selectors to target kebab-case class names

Tests:

• Adjust unit tests to expect updated kebab-case Stack item class names

[sourcery-ai]

Reviewer's Guide

Refactors the Stack component by renaming its CSS classes from underscore to hyphen format, updating sample stylesheet selectors, component class builders, and corresponding unit tests to reflect the new naming convention.

Class Diagram: Modified CSS Helper Members in Stack Class

classDiagram
  class Stack {
    -ClassString: string
    -ItemClassString(item: StackItem): string $
  }

Loading

State Diagram: CSS Class Name Changes in Stack Component

stateDiagram-v2
  direction LR
  state "bb_stack" as old_stack_class
  state "bb-stack" as new_stack_class
  state "bb_stack_item" as old_item_class
  state "bb-stack-item" as new_item_class

  old_stack_class --> new_stack_class : Renamed
  old_item_class --> new_item_class : Renamed

Loading

File-Level Changes

Change	Details	Files
Rename CSS class identifiers from underscore to hyphen for the Stack component	Updated deep CSS selectors in sample stylesheet: replaced .bb_stack/.bb_stack_item with .bb-stack/.bb-stack-item Modified CssBuilder in Stack.razor.cs to use "bb-stack" instead of "bb_stack" for the component root Adjusted ItemClassString in Stack.razor.cs to build "bb-stack-item" instead of "bb_stack_item" Updated unit test assertions in StackTest.cs to expect "bb-stack-item" class names	src/BootstrapBlazor.Server/Components/Samples/Stacks.razor.css src/BootstrapBlazor/Components/Stack/Stack.razor.cs test/UnitTest/Components/StackTest.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6188	Rename the CSS class bb_stack to bb-stack.	✅
#6188	Rename the CSS class bb_stack_item to bb-stack-item.	✅
#6188	Rename the C# class bb_stack to bb-stack.	✅

Possibly linked issues

• feat(Stack): rename bb_stack to bb-stack #6188: The PR implements the renaming change requested in the issue.

---

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

• 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 and they look great!

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

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6189   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          704       704           
  Lines        31099     31099           
  Branches      4394      4394           
=========================================
  Hits         31099     31099           

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.