Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: Show hunk context in expandable separators

Open
#1,100 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
60/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start by searching the codebase for line-info and line-info-basic to find the separator rendering and expansion controls, then read the related tests. Check how hunk metadata after @@ is represented and whether the existing tests cover both separator modes. Done when the hunk context appears alongside the unmodified-line count and expansion controls continue to work.

Written by the indexing model from the issue text.

Description

enhancement
Prerequisites
Proposal

Provide a way to display the hunk context (function/class names, etc.) in the line-info and line-info-basic separators.

For example, given:

   @@ -70,6 +70,11 @@ def update_profile

The separator could display both 16 unmodified lines and def update_profile and maintain the existing expansion controls.

Currently the built-in modes require choosing between:

  • Expansion controls, but only showing N unmodified lines
  • full metadata but losing expansion controls
Motivation and context

In files with several changes, the current N unmodified lines gives distance but not semantic meaning to where the diff is located. The text following the @@ often identifies the enclosing function or class and gives important context.

Dominant language
TypeScript
Stars
6.2k
Forks
226
Avg merge
1d 13h
Merged PRs (30d)
33

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pierrecomputer/pierre

All issues in pierrecomputer/pierre

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.