Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Feature request: opt-in no-wrap / horizontal-scroll for long lines in split view

Abierto
  • ¿Algo no está bien?
#238 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
react, typescript
Área
frontend

Línea de trabajo

Start by tracing split view rendering with viewType="split", including the single table, library-owned col elements, and the renderToken injection point described in the issue. Compare the existing renderToken workaround with the requested options, and consider the work complete when an opt-in no-wrap mode, stable per-line hook, or documented current-layout guidance supports the intended horizontal-scroll behavior.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hi, and thanks for the library — it powers the diff viewer in our code-review product.

Problem

In split (viewType="split") view, long code lines always soft-wrap onto multiple visual rows. We'd like the option to keep each line on one row and let it scroll horizontally instead. There doesn't appear to be a supported way to do this today.

Why it's hard to work around

The split view renders both panes inside a single 4-column

with table-layout: fixed; width: 100% and library-owned elements. As a result:

  • white-space: pre on the code cell just overflows/bleeds into the adjacent cell — the table never widens, so overflow-x: auto has nothing to scroll.
  • min/max-width on <td> is ignored per spec; only <col> widths constrain columns, and those are owned by the component template.
  • There's no per-line wrapper element around the code tokens (they render directly into the <td>), so the only injection point is a synthetic token via renderToken — which works but is fragile.

We found a workaround using renderToken + a CSS transform driven by custom scrollbars, but it's brittle and fights the table layout.

What would help (any one of these):

  1. A prop like wrapLines={false} / nowrap that switches long lines to horizontal-scroll.
  2. A stable per-line wrapper element (or a documented render hook) so consumers can control overflow/scroll per code cell.
  3. Guidance on achieving independent per-pane horizontal scroll with the current single-table split layout, if it's already possible.

Environment: react-diff-view 3.3.3, React 18, split view, parseDiff + tokenize.

Happy to share a minimal repro or a PR sketch if that's useful. Thanks!

Lenguaje dominante
TypeScript
Estrellas
1k
Forks
88
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de otakustay/react-diff-view

Todos los issues de otakustay/react-diff-view

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.