Skip to content

97 task repareer layout fout in side panel - #125

Merged
peereflits merged 5 commits into
developfrom
97-task-repareer-layout-fout-in-side-panel
Jul 15, 2025
Merged

97 task repareer layout fout in side panel#125
peereflits merged 5 commits into
developfrom
97-task-repareer-layout-fout-in-side-panel

Conversation

@DphnZwp

@DphnZwp DphnZwp commented Jul 14, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Style
    • Updated form and detail layouts to use a unified 12-column grid system for improved consistency and flexibility.
    • Renamed column span CSS classes from "column-span-N" to "col-N" across components.
    • Enhanced responsive behavior so form columns now span the full width on smaller screens.
    • Minor visual adjustments to form and grid layouts for a more streamlined appearance.
    • Replaced previous grid layout classes with a simplified and extended set of column span utilities.

@DphnZwp
DphnZwp requested review from peereflits and vdboots July 14, 2025 06:53
@DphnZwp DphnZwp self-assigned this Jul 14, 2025
@DphnZwp DphnZwp linked an issue Jul 14, 2025 that may be closed by this pull request
4 tasks
@coderabbitai

coderabbitai Bot commented Jul 14, 2025

Copy link
Copy Markdown
Contributor

"""

Walkthrough

The changes update the grid layout system for form and detail components by renaming and expanding column span CSS classes from .column-span-N to .col-N, and updating related C# methods to generate the new class names. The layout now uses a 12-column grid for improved consistency and responsive behavior.

Changes

Files Change Summary
.../Detail/InnovativeDetail.razor.cs
.../Form/InnovativeForm.razor.cs
Updated GetColumnWidthClass methods to return "col-N" instead of "column-span-N" for column width classes.
.../Detail/InnovativeDetail.razor.css
.../Form/InnovativeForm.razor.css
Replaced .column-span-N with .col-N classes, switched to a 12-column grid, reworked responsive and group styles.
.../Form/InnovativeForm.razor Changed main section class from "rz-dialog-side-content-layout" to "innovative-grid-layout", removed <br/>.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant FormComponent
    participant CSSGrid

    User->>FormComponent: Render form with columns
    FormComponent->>FormComponent: Call GetColumnWidthClass(columnGroup)
    FormComponent->>CSSGrid: Apply "col-N" class to column
    CSSGrid-->>User: Display columns in 12-column grid layout
Loading

Suggested reviewers

  • vdboots
  • peereflits

Poem

In grids of twelve, our columns align,
With "col-N" classes, the forms now shine.
Old spans retired, new layouts unfold,
Responsive and neat, a sight to behold.
🐇 Hopping through code, we tidy and mend—
On CSS winds, improvements ascend!
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 881babc and 572e374.

📒 Files selected for processing (2)
  • Src/Innovative.Blazor.Components/Components/Detail/InnovativeDetail.razor.css (1 hunks)
  • Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.css (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • Src/Innovative.Blazor.Components/Components/Detail/InnovativeDetail.razor.css
  • Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.css
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: submit-nuget

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai 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.

Actionable comments posted: 2

🔭 Outside diff range comments (2)
Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor (1)

12-16: Exception panel still references obsolete .column-span-4 class

All other components moved to the new col-* utilities, but the alert section kept the removed selector.
Without a matching rule it will collapse to the default (one column) and break the layout.

- <section class="rz-alert rz-background-color-danger-lighter gap-2 column-span-4">
+ <section class="rz-alert rz-background-color-danger-lighter gap-2 col-4">
Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.css (1)

116-118: Outdated selector inside media query

The form wrapper class was renamed to .innovative-grid-layout, but the scoped rule still targets .rz-dialog-side-content-layout ::deep .rz-label.
Update the selector or the margin hack will never apply on small screens.

🧹 Nitpick comments (6)
Src/Innovative.Blazor.Components/Components/Detail/InnovativeDetail.razor.cs (1)

49-52: Validate width range before composing col-* class

column.Width comes from user data (FormModel.Columns). Guard against values ≤ 0 or > 12 to avoid emitting an invalid class that has no CSS definition.

- return $"col-{column.Width}";
+ return column.Width is > 0 and <= 12
+        ? $"col-{column.Width}"
+        : string.Empty;
Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.cs (1)

124-132: Same width-range guard recommended

The helper now mirrors InnovativeDetail, but it would still return col-13 etc. if bad data slips in. Please apply the same range validation here for consistency.

Src/Innovative.Blazor.Components/Components/Detail/InnovativeDetail.razor.css (2)

38-42: Duplicate .col-6 definition – safe but noisy

Lines 33-41 and 38-42 repeat the exact rule‐set for .col-6.
Consider removing the second block to keep the stylesheet concise.


58-61: Duplicate .col-9 definition

Same redundancy as above; drop the duplicate.

Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.css (2)

38-42: Remove duplicate .col-6 rule

Identical to the block at 33-36.


58-61: Remove duplicate .col-9 rule

Identical repetition.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e044c52 and b04260f.

📒 Files selected for processing (5)
  • Src/Innovative.Blazor.Components/Components/Detail/InnovativeDetail.razor.cs (1 hunks)
  • Src/Innovative.Blazor.Components/Components/Detail/InnovativeDetail.razor.css (1 hunks)
  • Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor (1 hunks)
  • Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.cs (1 hunks)
  • Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.css (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor (1)
Learnt from: peereflits
PR: innovative365nl/SharedBlazorCompoments#116
File: Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.cs:327-340
Timestamp: 2025-07-07T14:57:57.097Z
Learning: In the NotifyPropertyChanged method in InnovativeForm.razor.cs, the early return after notifying the first property implementing INotifyFormValueChanged is intentional design. Only one property changes at a time, so the method only needs to notify the first available listener.
Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.css (1)
Learnt from: peereflits
PR: innovative365nl/SharedBlazorCompoments#116
File: Src/Innovative.Blazor.Components/Components/Form/InnovativeForm.razor.cs:327-340
Timestamp: 2025-07-07T14:57:57.097Z
Learning: In the NotifyPropertyChanged method in InnovativeForm.razor.cs, the early return after notifying the first property implementing INotifyFormValueChanged is intentional design. Only one property changes at a time, so the method only needs to notify the first available listener.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: test

@DphnZwp
DphnZwp marked this pull request as draft July 15, 2025 06:51
@DphnZwp
DphnZwp marked this pull request as ready for review July 15, 2025 06:53
@sonarqubecloud

Copy link
Copy Markdown

@peereflits

peereflits commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

In de example app van shared components, zie

  • Side panel (simple) / Dialog Example 1
  • Side panel (advanced) / Dialog Example 2
    => open dialog , klik "edit".
image

Wordt opgelost in #127 door vdBoot

@peereflits
peereflits merged commit 492a9d1 into develop Jul 15, 2025
3 of 4 checks passed
@MatthijsvanderPlas
MatthijsvanderPlas deleted the 97-task-repareer-layout-fout-in-side-panel branch September 4, 2025 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[TASK] Repareer layout fout in side panel

2 participants