Dictation failures: Retry beside the banner, Open Dictate… on the card, dismissable History note
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Three separate changes in the Swift macOS app: the Dictate banner in Views.swift (around lines 41-58), the failure card in CapturePanel.swift (around 1126-1130, with its registry entry and docs/floating-toolbar.md:70), and the History note in HistoryView.swift (around line 380) with dismissError() in AppModel.swift. Start by reading the existing Retry action in the Capture recovery section (around :345-371) and AppModel's recovery state. Done means the gallery assertions and check-surfaces.py pass, and the accessibility press clears the History attention.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Outcome: a recoverable dictation failure offers Retry where it says “kept for retry”. The floating card's door is named for where it goes, and History's problem note can be put away.
1. Banner Retry
- Problem: the Dictate banner (Views.swift:41-58) offers only Report and ×. Retry sits in the collapsed Capture recovery section (:18, :345-371), even though AppModel.swift:449-452 says the audio was kept for retry.
- Change: on the Dictate page, when there is a current recovery and
canRetryis true, show Retry transcription. It uses the same action as the section's Retry. - Check: a gallery assertion; no Retry on the dictionary page.
2. Open Dictate…
- Problem: the failure card's “Open Workbench” (CapturePanel.swift:1126-1130) opens Dictate. The same words open Home in the panel footer (WorkbenchQuickPanel.swift:121). For the same failure, the panel row says Open Dictate… (:328).
- Change: rename the card's button and set its registry entry to
belongsTo: dictate. Update docs/floating-toolbar.md:70. - Check: check-surfaces.py and the render.
3. History dismiss
- Problem: the note at HistoryView.swift:380 cannot be dismissed, unlike Dictate's (Views.swift:55) and Meetings' (MeetingWorkspaceView.swift:183). It also pins the panel row (WorkbenchQuickPanel.swift:141).
- Change: put the note and an × calling
dismissError()in a card. Reword the comment at AppModel.swift:941. - Check: in the gallery, an accessibility press clears the attention.
Value before scope
- Outcome: failures can be recovered from where they are shown. Evidence: the code cited above.
- Simpler route: reuse the existing actions.
- Owner: AppModel's recovery and attention.
- Complexity: one button, one rename, one ×.
- Verified by: gallery and surface checks.
Grammar: Quality.
Refs #134, Refs #156
Build-ready record from the overnight lead session of 15 Oct 2026, verified against main edc15df by an independent skeptic per item. Implementation follows on a claude/* branch; this issue closes only after native acceptance.
- Lenguaje dominante
- Swift
- Estrellas
- 0
- Forks
- 1
- Merge medio
- 8 h 5 min
- PR fusionados (30 d)
- 215
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Ship-Work/workbench
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
documentation good first issue help wanted
Dificultad 2/5 Medio día Aptitud para principiantes 74/100
Ship-Work/workbench#29 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
Los mantenedores suelen responder en 1 día
Todos los issues de Ship-Work/workbench
Issues similares
-
binding:web core docs p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
RunanywhereAI/runanywhere-sdks#1123 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Countly/countly-sdk-ios#485 ·
Los mantenedores suelen responder en 1 día
-
area:ui enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
s3onghyun/bulchimbeon#22 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día