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

Analysis Catalog: morpheme rows

Abierto
  • ¿Algo no está bien?
#189 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
typescript
Área
frontend

Línea de trabajo

Comienza con analysis-identity.ts y el trabajo existente de Analysis Catalog de #186; después, rastrea cómo se gestionan TokenAnalysis.morphemes y mergeIntoIdenticalPayload. Define la identidad de la fila de morfema y la unión de usos, y asegúrate de que se representen los recuentos independientes, la ordenación, el filtrado, la edición de gloss/ref y la eliminación únicamente del análisis. La finalización incluye hacer visibles las cascadas cuando las ediciones fusionan análisis de tokens.

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

Descripción

enhancement

Add a morpheme list to the Analysis Catalog (#186), so morphemes can be counted, sorted, and edited independently of the words that contain them.

What is already reachable without this

Morpheme data is not invisible in the token-only catalog: morphemes render as detail inside a token row, and token search matches morpheme forms and glosses. Typing DAT.SG already finds the words that use it.

What is missing is everything that needs a morpheme to be its own row:

  • independent counts and sorting ("how many times have I used DAT.SG across all words?")
  • filtering to bare-form morphemes — split out but never glossed, which is real unfinished-work triage
  • a global morpheme gloss edit that fixes every containing analysis at once

Why this is the hardest of the three lists

MorphemeAnalysis is not a payload. It is a nested array inside TokenAnalysis.morphemes, with an id unique only within that array, no link table, and no dedupe. So:

  • Identity has to be derived. Group by the projection that already exists — morphemeIdentity in analysis-identity.ts (form + gloss + entryRef / senseRef / allomorphRef / grammarRef). This makes the catalog its second consumer; keep the two in step.
  • Usage locations are a union. A morpheme row's locations are the locations of every containing token analysis.
  • Editing fans out and can cascade. Writing a morpheme gloss into M containing TokenAnalysis payloads can make several of them content-identical to other analyses, firing mergeIntoIdenticalPayload. Editing one morpheme row can silently collapse several token rows into each other. That has to be surfaced, not silently applied.

Delete semantics: clears the analysis, keeps the parse

Deleting a morpheme row removes the analysis, not the morpheme. The M morphemes lose their gloss and lexicon refs; form and position stay. The row -ῇ -> DAT.SG (40) disappears and -ῇ -> (unglossed) (40) appears. Every parse stays intact.

Rejected: removing the morpheme from each parse. That leaves M breakdowns that no longer decompose their word, and it fires the cascade above as a second surprise from one click. Re-cutting a word is what the morpheme editor on the token chip is for, where the whole word is visible.

This keeps delete meaning one thing everywhere: it removes recorded analysis, never the shape of the text or its decomposition.

Note on breakdown editing

Editing how a word is cut stays on the token row, not here — that is a property of the token analysis, and one edit there already fixes every usage. A morpheme row edits a morpheme's gloss and refs. Two different questions about two different objects, which is why they are separate lists.

Follow-up to #186.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
0
Merge medio
2 d 5 h
PR fusionados (30 d)
46

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 sillsdev/interlinearizer-extension

Todos los issues de sillsdev/interlinearizer-extension

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.