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

Add fixtures for the erase modes we have no coverage of (clean-screen, area erase)

Abierto
  • ¿Algo no está bien?
#73 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start with tests/input/README.md and compare the existing erase.note/erase.pdf and stroke-isolation.note/.pdf fixture patterns. Capture area erase, clean screen, and the lasso select-and-move versus lasso erase pair with untouched controls, recording device and firmware. Done means adding the new .note fixtures and matching Supernote PDF exports for the modes needed by #70 and #72.

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

Descripción

Split out from #69 (Part 1.4 of plans/vector-format-spec.md).

flutter_note_lib.dll's redraw path names the trail categories the device recognises. Comparing that list against our fixtures shows two we have never captured:

Device category Our coverage
ERASE_LINE_COLOR_VALUE (the color == 255 line eraser) yes — erase.note, horizontal_1270.note
region selection / ERASER select yes — nomad-3.26.40-link-tag-3p.note p3
this is five star yes — fiveStarsSignal
this is normal trail yes
TRAIL_ERASE_AREA (area erase as a category distinct from the line eraser) none
CLEAN SCREEN (whole-page erase) none

Why it matters

These are the fixtures #70 and #72 need. The erase-vs-select discriminator can't be isolated by diffing records if we only have one side of the comparison, and m_trailStatus's codes can't be mapped to meanings without a note that exercises each mode deliberately.

There's also a plain correctness question: we don't know what vectorInk currently does with a whole-page erase. erase-no-white-pen.note covers "page whose ink layers are empty" and renders nothing, which may already be the same statement at page scale — but that was reached by a different route and hasn't been checked against a real CLEAN SCREEN record.

What to capture

For each mode, ideally on the same page as untouched control strokes, plus Supernote's own PDF export as ground truth (the pattern erase.note/erase.pdf and stroke-isolation.note/.pdf already follow):

  1. Area erase — the rectangular/region erase tool, over some strokes and partially over others.
  2. Clean screen — write content, then whole-page erase. Worth capturing both as the only page and as one page among several.
  3. Lasso select-and-move vs lasso erase of visually identical content, as the direct differential pair for #70.

Note per tests/input/README.md conventions: record which device and firmware, since the record tail already varies four ways across generations.

Lenguaje dominante
TypeScript
Estrellas
42
Forks
9
Merge medio
30 min
PR fusionados (30 d)
2

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 philips/supernote-typescript

Todos los issues de philips/supernote-typescript

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.