Skip to content

fix(tui): bottom-align the access join and share the helper-text indent - #26

Merged
NovusEdge merged 1 commit into
mainfrom
tui-polish-access-fields
Aug 9, 2026
Merged

fix(tui): bottom-align the access join and share the helper-text indent#26
NovusEdge merged 1 commit into
mainfrom
tui-polish-access-fields

Conversation

@NovusEdge

Copy link
Copy Markdown
Owner

Two small polish fixes from the TUI review.

access.gojoinAccess joined the two panes with a literal " " element. That spacer is a one-line-tall block inside the horizontal join, so the shorter pane's bottom sat ragged. Moved the gap onto the access pane with MarginLeft(2) so JoinHorizontal(lipgloss.Top, …) aligns both to the top cleanly.

fields.go — the gray hint rendered at the value column while note rendered at the label column, so the two helper texts didn't line up. Moved note to the value column to match hint.

just check and just test pass.

joinAccess used a literal two-space string as a JoinHorizontal argument,
leaving the shorter pane's bottom ragged. A MarginLeft(2) style on the
access pane keeps the gap without a spacer block.

fields.note() indented to the label column while fields.hint() indented
to the value column, so a screen using both had misaligned gray text.
note() now uses the value column.
@NovusEdge NovusEdge added the enhancement New feature label Aug 9, 2026
@NovusEdge NovusEdge self-assigned this Aug 9, 2026
@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 17 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 907b6426-a7ad-43e3-bf46-fdd0accc51c2

📥 Commits

Reviewing files that changed from the base of the PR and between ed1a0e2 and 18a03aa.

📒 Files selected for processing (2)
  • internal/tui/access.go
  • internal/tui/fields.go

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

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

@NovusEdge
NovusEdge merged commit eb8889b into main Aug 9, 2026
8 checks passed
@NovusEdge
NovusEdge deleted the tui-polish-access-fields branch August 9, 2026 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant