Feature: CodeView should support per-item header heights
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the CodeView implementation and its tests, then trace how item height estimation, sticky-header positioning, and scroll calculations currently use header sizes. The issue does not name specific files or tests, so first map those code paths. Done means CodeView supports a per-item diffHeaderHeight for all three calculations without scroll jumps when header sizes vary.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have searched for duplicate or closed feature requests
- I have read the contributing guidelines
Proposal
Allow CodeView items to specify or resolve a diffHeaderHeight. CodeView should use it for item height estimation, sticky-header positioning, and scroll calculations.
Motivation and context
I'd like to render file-level annotations, or alternate content for collapsed files, which would look better as a part of the header rather than an annotation that is indented for the line-number column. This would require that we can specify a per-item header size though as right not it causes jumps in the scrolling when headers are not a consistent size.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 226
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 39
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 pierrecomputer/pierre
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pierrecomputer/pierre#1187 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pierrecomputer/pierre#1150 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
pierrecomputer/pierre#1228 ·
Maintainers usually reply within 1 day
-
KDL language supportOpen
Difficulty 3/5 1-2 days Newbie friendliness 59/100
pierrecomputer/pierre#1222 ·
Maintainers usually reply within 1 day
-
Feature: Make find and replace discoverable from the search panelPossibly taken @danipen claimed this 2 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
pierrecomputer/pierre#1220 ·
Maintainers usually reply within 1 day
All issues in pierrecomputer/pierre
Similar issues
-
[Bug]: Device screenshot fails with 500 on iPhone Duo (Xcode 27.2): serve-sim calls simctl without --displayPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
pingdotgg/t3code#24900 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inu-appcenter/UNIDorm-web#411 ·
Maintainers usually reply within 1 day
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ranxianglei/billion-context#4720 ·
Maintainers usually reply within 1 day
-
area:arcade game p3-medium ready-for-agent type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
fderuiter/deruiter.dev#2840 ·
Maintainers usually reply within 1 day