Comments that apply to a whole file or the whole diff, not a line
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start by locating the existing line-comment UI and the import/export paths that serialize anchors. Review the /diffx-finish-review skill documentation as part of the scope. Done means file- and diff-level comments work without changing line comments, older exports still import, and duplicate detection includes scope.
Written by the indexing model from the issue text.
Description
Summary
Every comment is anchored to a line (or line range, #33). Observations about a file as a whole ("this module should be split") or the change as a whole ("missing migration") have no anchor, so reviewers attach them to an arbitrary line.
Proposal
- File-level comment: a "Comment" button in each file header, anchored to the file path only.
- Diff-level comment: a "Comment on diff" button above the first file, anchored to nothing.
- "Copy comments" emits
<comment scope="file">inside the<file>block and<comment scope="diff">outside all<file>blocks. Import parses both and de-duplicates on scope as well as anchor. - Line comments are unchanged on disk and in export (
scopeabsent meansline).
Compatibility
Older exports import unchanged. The /diffx-finish-review skill documentation requires an update for the two new scopes. A PR follows.
- Dominant language
- TypeScript
- Stars
- 206
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
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 wong2/diffx
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Doist/todoist-cli#576 ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/aimock#491 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
agilepathway/label-checker#710 · 2 comments ·
Maintainers usually reply within 1 day