Prevent rendering any element when no renderable child content provided in BitMediaQuery (#10943)

[msynk]

closes #10943

Summary by CodeRabbit

• Bug Fixes

  • Improved the BitMediaQuery component to avoid rendering empty containers when no content is provided.

• Style

  • Enhanced the display of media query match status in the demo by adding a descriptive label and bold formatting for better clarity.

[coderabbitai]

Walkthrough

The changes update the BitMediaQuery component to render nothing when no content fragments are provided, instead of always rendering an empty wrapper. The demo and its code sample are updated to display a more descriptive label for the media query match status, including formatting and query name.

Changes

File(s)	Change Summary
src/BlazorUI/Bit.BlazorUI/Components/Utilities/MediaQuery/BitMediaQuery.razor	Updated rendering logic to conditionally render the wrapper <div> only if at least one content fragment exists.
src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Pages/Components/Utilities/MediaQuery/BitMediaQueryDemo.razor src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Pages/Components/Utilities/MediaQuery/BitMediaQueryDemo.razor.cs	Updated display and example markup for the media query match status to include a descriptive label and formatting.

Sequence Diagram(s)

sequenceDiagram
    participant ParentComponent
    participant BitMediaQuery

    Note over ParentComponent: Parent renders BitMediaQuery

    ParentComponent->>BitMediaQuery: Render with content fragments (Matched, ChildContent, NotMatched)
    alt At least one fragment provided
        BitMediaQuery-->>ParentComponent: Render <div> with appropriate content
    else No fragments provided
        BitMediaQuery-->>ParentComponent: Render nothing
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
BitMediaQuery should not render anything when no renderable child elements are provided (#10943)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Poem

A rabbit hopped through Blazor code,
Where wrappers once would always show'd.
Now if content's not in sight,
The component stays out of the light.
With labels bold and queries neat,
This update makes the UI sweet! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 35ce25a and f0acb7e.

📒 Files selected for processing (3)

• src/BlazorUI/Bit.BlazorUI/Components/Utilities/MediaQuery/BitMediaQuery.razor (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Pages/Components/Utilities/MediaQuery/BitMediaQueryDemo.razor (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Pages/Components/Utilities/MediaQuery/BitMediaQueryDemo.razor.cs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build and test

🔇 Additional comments (3)

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Pages/Components/Utilities/MediaQuery/BitMediaQueryDemo.razor (1)

76-76: Enhanced demo display improves user experience.

The updated label provides better context by showing the specific query name and uses bold formatting for clearer visual distinction of the match status.

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Pages/Components/Utilities/MediaQuery/BitMediaQueryDemo.razor.cs (1)

210-210: Code example updated to match demo implementation.

Good practice to keep the example code string consistent with the actual demo markup for accurate documentation.

src/BlazorUI/Bit.BlazorUI/Components/Utilities/MediaQuery/BitMediaQuery.razor (1)

4-20: Excellent conditional rendering implementation.

This change perfectly addresses the PR objective by preventing empty div rendering when no content fragments are provided. The logic correctly uses null-coalescing operators to check if any of the three content options (Matched, ChildContent, or NotMatched) contains renderable content. The internal rendering logic remains unchanged, preserving existing behavior when content is present.

This improvement enhances performance by avoiding unnecessary DOM elements and provides cleaner HTML output.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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