Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#73 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
40
Fork
9
Merge medio
8g 1h
PR unite (30g)
2

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di philips/supernote-typescript

Tutte le issue di philips/supernote-typescript

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.