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

Dictionary: update an existing phrase instead of saving conflicting duplicate rules

Abierto
  • ¿Algo no está bien?
#175 2 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
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
macos, swift
Área
desktop

Línea de trabajo

Start with Dictionary mutation in Sources/LocalVoice/AppModel.swift, then read the identity and validation logic in CorrectionRule.swift and sequential replacements in TextPrimitives.swift; inspect the Dictionary UI in Views.swift and the related work in #164. Verify the actual add/update route, both Dictionary and Remember validation, and isolated duplicate recovery; done means updates preserve rule identity/order, legacy conflicts require explicit resolution, and native acceptance leaves no fixture in user data.

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

Descripción

Outcome and priority

P2 functional defect. Saving a corrected spelling for an existing phrase should update that phrase deliberately, rather than leave two contradictory rules where the old spelling wins.

Evidence

Preview 2.3.0, build 20260928054038, clean source 00be555139f87d4557f48fcffc132b8621c251a2; macOS 26.5.1 (25F80), built-in display. Verified through Copy build details in the running app and bundle metadata.

Source plus an isolated execution of production code: Dictionary Add only trims/checks nonempty and appends (AppModel). A temporary Swift harness used the exact TextPrimitives.swift and CorrectionRule.swift from the installed commit with two synthetic rules:

  • qa velcor 928 → VelcorOne928
  • QA VELCOR 928 → VelcorTwo928

TextRules.apply returned Please ask VelcorOne928 tomorrow. The later intended spelling was ignored. CorrectionRule.propose for that phrase then returned duplicateRules with count 2.

The worker ran the interpreter in an isolated temporary directory; it did not build/launch Workbench or touch the live dictionary. Parent inspected the exact mutation and rule-application paths. Native inspection additionally found Add enabled for identical Heard and Write text; those unsaved fields were cleared. No real saved rule was added or removed.

Starting points: sequential replacements, Dictionary UI, existing correction validation and identity.

Chosen behaviour

Use the same phrase identity and validation in Dictionary and Remember correction. An exact existing pair is idempotent. A different output for the same case-insensitive phrase shows the current value and an explicit Update action; updating preserves the rule ID and unrelated order.

Legacy contradictory duplicates remain intact until an explicit focused resolution chooses the desired output. Show the conflicting values so people can resolve them without guessing rule order. Do not replay unrelated rules into the current transcript just because a future dictionary rule changed.

Acceptance

  • Exact re-adds and changes only to Heard casing do not create duplicate entries. Changes to Write casing can be intentional and offer Update, preserving the exact chosen output.
  • Update changes future TextRules output to the chosen spelling and retains rule identity/order.
  • Dictionary and Remember correction agree on no-op, newline/control, empty and oversized validation.
  • Legacy duplicates can be resolved explicitly without silent deletion of unrelated entries.
  • Cover the actual Dictionary mutation route, reusing CorrectionRule logic. Existing CorrectionRuleChecks alone leave addReplacement unprotected.
  • Native-test synthetic add/update/duplicate recovery using an isolated disposable library, then verify no fixture remains in the user's data.
  • Record signed installed acceptance; the isolated algorithm run is not a native transcription test.

Coordination

Second-pass request under #164. #134 owns discovery/navigation and #15 first dictation; neither covers contradictory saved rules. Share the AppModel implementation owner with Read/recovery changes.

Lenguaje dominante
Swift
Estrellas
0
Forks
1
Merge medio
8 h 5 min
PR fusionados (30 d)
215

Preparar el entorno

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 Ship-Work/workbench

Todos los issues de Ship-Work/workbench

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.