Skip to content

Add text overflow modes and adaptive columns#40

Open
noponoponopo wants to merge 1 commit into
runcat-dev:mainfrom
noponoponopo:feat/custom-metrics-overflow-columns
Open

Add text overflow modes and adaptive columns#40
noponoponopo wants to merge 1 commit into
runcat-dev:mainfrom
noponoponopo:feat/custom-metrics-overflow-columns

Conversation

@noponoponopo

Copy link
Copy Markdown

Context of Contribution

  • Bug Fix
  • Refactoring
  • New Feature
  • Others

Summary of the Proposal

This pull request adds an optional textOverflow field to Custom Metrics snapshots.

Three behaviors are available:

  • truncate keeps text on one line without widening its column.
  • wrap uses multiple lines without widening its column.
  • expand allows content to widen its column.

The default is expand, which preserves the existing behavior.

The dashboard adds another column only when its content would exceed the visible screen height. Column heights are measured again after their widths are established so wrapped text is placed correctly.

A single card that exceeds the available height becomes internally scrollable.

All 136 tests pass.

Reason for the new feature

Custom Metrics values can contain long titles, paths, descriptions, or generated text. A single overflow behavior cannot serve both compact status cards and cards that need to display complete text.

The new modes let each producer choose between compact truncation, complete wrapped text, and the existing expanding behavior.

Adaptive columns keep larger sets of cards visible without requiring a permanently wider dashboard. The existing behavior remains the default, so current JSON files do not require migration.

Checklist

  • I have read the CONTRIBUTING.md and agree to follow it.
  • This PR does not contain commits of multiple contexts.
  • Code follows proper indentation and naming conventions.
  • Implemented using only APIs that can be submitted to the App Store.

Signed-off-by: nopo <dev@nopo1.com>
@noponoponopo

Copy link
Copy Markdown
Author

PR#37と#39が前提となっています

@noponoponopo

Copy link
Copy Markdown
Author

一連の4つのPR#37~#40を実装した場合の実際の見た目
はこのようになります。
screen 2026-07-16 2 03 52

@Kyome22

Kyome22 commented Jul 15, 2026

Copy link
Copy Markdown
Collaborator

I get the impression that this significantly departs from RunCat's philosophy of "simplicity."

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.

2 participants