The Dictation page's empty state still calls the figure "accuracy yesterday", which the rest of the app renamed "Left as dictated"
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
Research direction
Start at Sources/UttrflowUX/MainDictationPresentation.swift:438 and compare the chip caption with the existing accuracyTitle at lines 154-161. Update the expectation in Tests/UttrflowUXTests/MainDictationPresentationTests.swift:506, then run make verify with DEVELOPER_DIR set as described. Done means no user-facing string in Sources/UttrflowUX calls this figure accuracy and verification passes.
Written by the indexing model from the issue text.
Description
What happens
The figure built from how little clean-up changed is titled so it does not claim to be accuracy (see #153): DictationPresenter.accuracyTitle = "Left as dictated", with a caption saying it "does not say whether they were heard correctly" (Sources/UttrflowUX/MainDictationPresentation.swift:154-161). Insights uses the same title.
The chips under the empty Dictation page, which show yesterday's figures, still label the same number "accuracy yesterday" (Sources/UttrflowUX/MainDictationPresentation.swift:433-439).
Why it matters
The same number is called two different things on the same page, and the chip makes the claim the rename was made to remove.
Where to start
- Change the chip caption in
MainDictationPresentation.swift:438, for example to "left as dictated yesterday". - Update
Tests/UttrflowUXTests/MainDictationPresentationTests.swift:506. - Run
make verify(exportDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developerfirst); CONTRIBUTING.md has the rest.
Acceptance criteria
- No user-facing string in
Sources/UttrflowUXcalls this figure "accuracy". - The test pins the new caption;
make verifypasses.
Size: XS, under an hour.
- Dominant language
- Swift
- Stars
- 4
- Forks
- 17
- Avg merge
- 18h 15m
- Merged PRs (30d)
- 442
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uttrflow/uttrflow-swift
-
Docs/performance.md says the clipboard panel waits for catchUp; toggleQuickPanel no longer waits Openarea:docs documentation good first issue P2
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
uttrflow/uttrflow-swift#1032 ·
-
area:docs documentation good first issue P2
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
uttrflow/uttrflow-swift#1023 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uttrflow/uttrflow-swift#827 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
uttrflow/uttrflow-swift#802 ·
-
area:general enhancement good first issue P2
Difficulty 2/5 Under an hour Newbie friendliness 92/100
uttrflow/uttrflow-swift#755 ·
All issues in uttrflow/uttrflow-swift
Similar issues
-
type: docs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
googleapis/google-cloud-swift#971 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35743 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
manaflow-ai/cmux#13417 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ionic-team/capacitor#8616 ·