fix(EditorForm): parameter LabelWidth not work when set GroupOrder

[ArgoZhang]

Link issues

fixes #6983

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

Bug Fixes:

• Restore label width behavior for EditorForm when grouping items by adding inline style binding to the group container

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR fixes the issue where the LabelWidth parameter was ignored when using GroupOrder by ensuring the FormStyleString (which includes label width) is applied directly to each group container.

Class diagram for updated EditorForm group rendering

classDiagram
class EditorForm {
  - FormClassString: string
  - FormStyleString: string
  + RenderGroupItems: RenderFragment<KeyValuePair<string, IOrderedEnumerable<IEditorItem>>>
  + GetRenderTemplate(item: IEditorItem): RenderFragment
}
class GroupBox {
  + Title: string
}
EditorForm "1" -- "*" GroupBox: renders

Loading

File-Level Changes

Change	Details	Files
Apply FormStyleString to group container so LabelWidth takes effect when grouping	Add style attribute binding for FormStyleString on the group container div	src/BootstrapBlazor/Components/EditorForm/EditorForm.razor

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6983	Ensure that the LabelWidth parameter works correctly when GroupOrder is set in EditorForm.	✅

Possibly linked issues

• bug(EditorForm): parameter LabelWidth not work when set GroupOrder #6983: The PR applies FormStyleString to the group container, fixing LabelWidth not working with GroupOrder.

---

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.

[Copilot]

Pull Request Overview

This PR fixes a bug where the LabelWidth parameter was not being applied correctly when GroupOrder was set in the EditorForm component. The fix ensures that form styling is properly propagated to grouped items by adding the FormStyleString to the div element inside the GroupBox.

• Added FormStyleString to the div element within grouped items rendering

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sourcery-ai]

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

---

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 (6943c84) to head (12961e0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6984   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          741       741           
  Lines        32343     32352    +9     
  Branches      4481      4481           
=========================================
+ Hits         32343     32352    +9     

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.