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

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

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
macos, swift
Ambito
desktop

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Swift
Stelle
0
Fork
1
Merge medio
12h 29m
PR unite (30g)
201

Preparare l'ambiente

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

Tutte le issue di Ship-Work/workbench

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.