fix: tidy settings section spacing

[tariknz]

Description

Tidies the shared settings layout by removing compounded padding from titleless nested sections and the extra left padding on session bar reorder rows.

The previous layout applied section padding at every nesting level, which pushed drag handles and nested controls progressively farther right. Titled sections now retain their normal padding and vertical separation, while titleless sections act as layout-neutral groups. Empty heading elements are no longer rendered.

Architecture phase: not applicable; this is a presentation-only fix within the existing settings components and does not change application layering or data flow.

Validated with npm run lint and npm run build-storybook.

Screenshots

Before

Session bar drag handles and nested input settings were over-indented. Adjacent titled sections also lacked consistent separation.

After

Drag handles and nested controls align with their parent settings, while titled sections retain consistent spacing.

Type of Change

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Performance improvement
• Refactoring (no functional changes)
• Documentation update
• Dependency update

Checklist

• I have discussed this change in the discord server
• I have tested this in iRacing (either in an online session or with AI)
• All tests pass locally via npm test
• I have added tests that prove my fix is effective or that my feature works
• I have run npm run lint and fixed any issues
• I have performed a self-review of my own code
• I have added/updated Storybook stories for visual changes
• I have updated the README.md (if applicable)
• I have updated defaultDashboard.ts if introducing new widgets or configurations (if applicable)

[coderabbitai]

Warning

Review limit reached

@tariknz, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 44b92e85-4a7d-4c7d-b81c-2f8c926b6fd0

📥 Commits

Reviewing files that changed from the base of the PR and between f189c2e and 8562e55.

📒 Files selected for processing (2)

• src/frontend/components/Settings/components/SessionBarItemsList.tsx
• src/frontend/components/Settings/components/SettingSection.tsx

---

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

_{Comment @coderabbitai help to get the list of available commands.}