feat(Light): rename class name light to bb-light

[ArgoZhang]

Link issues

fixes #6231

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 the "light" CSS class to "bb-light" in the Light component to avoid naming conflicts, update corresponding SCSS styles and unit tests to reflect the new class name

Bug Fixes:

• Update unit tests in LightTest to assert against "bb-light" instead of "light"

Enhancements:

• Change Light component’s default CSS class from "light" to "bb-light" in its Razor code
• Rename the .light selector to .bb-light in Light component SCSS

[sourcery-ai]

Reviewer's Guide

This PR renames the default CSS class of the Light component from "light" to "bb-light" across source code, styling, and tests to resolve issue #6231 and ensure consistent naming conventions.

Updated Class Diagram for the Light Component

classDiagram
  class Light {
    #ClassString: string?
  }

Loading

File-Level Changes

Change	Details	Files
Refactored Light component’s default CSS class naming	Changed CssBuilder.Default from "light" to "bb-light" Updated SCSS selector from ".light" to ".bb-light"	Light.razor.cs Light.razor.scss
Updated unit tests to reflect class name change	Replaced occurrences of "light flash" with "bb-light flash" Adjusted assertions to no longer match old class names	LightTest.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6231	Rename the CSS class 'light' to 'bb-light' in the Light component.	✅

Possibly linked issues

• feat(Light): rename class name light to bb-light #6231: The PR renames the CSS class 'light' to 'bb-light' as requested in the issue, fixing issue feat(Light): rename class name light to bb-light #6231.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c926f58) to head (7bca70f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6232   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          704       704           
  Lines        31113     31113           
  Branches      4398      4398           
=========================================
  Hits         31113     31113           

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.

[sourcery-ai]

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

Prompt for AI Agents

Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `src/BootstrapBlazor/Components/Light/Light.razor.scss:1` </location>
<code_context>
-.light {
+.bb-light {
     --bb-light-bg: #{$bb-light-bg};
     --bb-light-danger-start-color: #{$bb-light-danger-start-color};
</code_context>

<issue_to_address>
Remove unexpected BOM before selector

An invisible BOM character is present before the selector, which may cause SCSS compilation errors. Please remove it.
</issue_to_address>

---

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.}

[sourcery-ai]

issue (bug_risk): Remove unexpected BOM before selector

An invisible BOM character is present before the selector, which may cause SCSS compilation errors. Please remove it.