style(ui): improve padding for VerticalTabItem #27251
Open
+11
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR improves the vertical padding behavior of
VerticalTabItemin the Settings sidebar to ensure better visual consistency across single-line and multi-line tab labels.Key improvements:
w-fullCode changes: The primary intentional change is:
Note on diff size: Additional lines in the diff are due to automatic code formatting performed by Biome/Prettier (import ordering, spacing normalization, fragment removal, etc.). These formatting changes do not modify any logic or behavior.
Visual Demo (For contributors especially)
cal.com.hover.ui.issue.mp4
| After

solved.mp4
-- | --
(Screenshot showing cramped multi-line items) | (Screenshot showing improved padding)
Changes Visible:
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
Steps to test:
py-autobehavior)w-full)Test configuration:
Checklist
<!-- Remove bullet points below that don't apply to you -->
What does this PR do?I haven't read the contributing guideMy code doesn't follow the style guidelines of this projectI haven't commented my code, particularly in hard-to-understand areasI haven't checked if my changes generate no new warningsMy PR is too large (>500 lines or >10 files) and should be split into smaller PRs