Skip to content

fix: The gap problem in the Toggle component #388 #389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ogzcode
Copy link
Contributor

@ogzcode ogzcode commented May 16, 2025

If there is no label with conditional rendering, label span was removed #388

Please check and give feedback. @Sqrcz @zoltanszogyenyi @cogor

Summary by CodeRabbit

  • Bug Fixes
    • Prevented empty label spans from being rendered when no label is provided.

Copy link

netlify bot commented May 16, 2025

Deploy Preview for sensational-seahorse-8635f8 ready!

Name Link
🔨 Latest commit 54ac486
🔍 Latest deploy log https://app.netlify.com/projects/sensational-seahorse-8635f8/deploys/68271f3591e85500082be352
😎 Deploy Preview https://deploy-preview-389--sensational-seahorse-8635f8.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

coderabbitai bot commented May 16, 2025

Walkthrough

A conditional rendering check was added to the label span in the FwbToggle component. Now, the span is only rendered if the label prop is non-empty, preventing the display of an empty span when no label is provided.

Changes

File Change Summary
src/components/FwbToggle/FwbToggle.vue Added conditional rendering to the label span based on the label prop.

Poem

A toggle with a label, clear and bright,
But if it's empty, it stays out of sight.
No more blank spans in the UI's light—
The code is now clean, the logic just right.
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 570e238 and 54ac486.

📒 Files selected for processing (1)
  • src/components/FwbToggle/FwbToggle.vue (1 hunks)

Comment on lines 9 to +10
<span :class="[toggleClasses, toggleSize, toggleColor]" />
<span :class="[toggleBallClasses, toggleBallOrder]">{{ label }}</span>
<span v-if="label" :class="[toggleBallClasses, toggleBallOrder]">{{ label }}</span>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

Conditional rendering on toggle ball span removes the thumb when no label.
The v-if="label" is applied to the span with toggleBallClasses, so the toggle thumb (ball) is not rendered if label is empty. We need to always render the ball and only conditionally render the text label in its own span.

Apply this diff to separate concerns:

-    <span :class="[toggleClasses, toggleSize, toggleColor]" />
-    <span v-if="label" :class="[toggleBallClasses, toggleBallOrder]">{{ label }}</span>
+    <span :class="[toggleClasses, toggleSize, toggleColor]" />
+    <span :class="[toggleBallClasses, toggleBallOrder]" />
+    <!-- Text label only shown when `label` is provided -->
+    <span v-if="label" class="ml-2 text-sm font-medium text-gray-900">{{ label }}</span>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<span :class="[toggleClasses, toggleSize, toggleColor]" />
<span :class="[toggleBallClasses, toggleBallOrder]">{{ label }}</span>
<span v-if="label" :class="[toggleBallClasses, toggleBallOrder]">{{ label }}</span>
<span :class="[toggleClasses, toggleSize, toggleColor]" />
<span :class="[toggleBallClasses, toggleBallOrder]" />
<!-- Text label only shown when `label` is provided -->
<span v-if="label" class="ml-2 text-sm font-medium text-gray-900">{{ label }}</span>
🤖 Prompt for AI Agents
In src/components/FwbToggle/FwbToggle.vue around lines 9 to 10, the span element
with toggleBallClasses is conditionally rendered based on the presence of label,
causing the toggle thumb to disappear when label is empty. To fix this, always
render the span with toggleBallClasses for the toggle thumb, and move the label
text into a separate span that is conditionally rendered only if label exists.

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.

1 participant