[Bug]: Side-by-side diff squeezes the "N unmodified lines" divider into the line-number column
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in the apps/web diff UI and compare how the “N unmodified lines” divider is rendered in unified and side-by-side views. Reproduce with collapsed unchanged lines in the PR pane’s Code tab, then check the divider’s width and styling. Done when side-by-side view shows the full label and divider line with matching line and hover styling.
Written by the indexing model from the issue text.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
- Open a diff with collapsed unchanged lines, for example in the PR pane's Code tab.
- Switch to side-by-side view.
- Look at the divider between two hunks.
Expected behavior
The divider spans the full width and reads "2 unmodified lines", with the same line and hover styling as in the unified view.
Actual behavior
The label is squeezed into the left line-number column and cut off to "2 u". The rest of the row is blank, with no divider line.
Impact
Cosmetic issue
Version or commit
0.0.46-nightly.20261008.2813
Environment
macOS, desktop app
Screenshots, recordings, or supporting files
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 13h 9m
- Merged PRs (30d)
- 271
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
[Bug]: Local environment can't be turned back on once disabled (toggle hidden behind "No environment selected")Possibly taken A pull request linked to this issue is open or already merged. Openbug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pingdotgg/t3code#17013 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Bug]: T3 Connect doc says held webhooks are kept per environment, but the relay keeps one inbox per linkPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation via-triage
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
pingdotgg/t3code#16995 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: T3 Connect doc gives the relay webhook path as /v1/hooks/:environmentId/..., but the relay routes on :endpointKeyPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation via-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pingdotgg/t3code#16988 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
pingdotgg/t3code#16881 · 1 comment ·
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vectorize-io/hindsight#5457 ·
Maintainers usually reply within 1 day
-
beginner friendly community contributions-welcome good first issue hacktoberfest help wanted testing up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lukilabs/beautiful-mermaid#160 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
rescript-lang/rescript-lang.org#1420 ·
Maintainers usually reply within 2 days