Audit report PDF still says "Layout flags" after the UI rename to "Layout warnings"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in src/lib/pdf/render-audit-report.ts at line 193 and the comment near line 268, then search with grep -rn "Layout flags" src. Check the audit-report tests or snapshots for the old string, update them as needed, and run the audit-report tests. Done means the PDF and source user-visible text use "Layout warnings" while historical docblock references are allowed.
Written by the indexing model from the issue text.
Description
Problem
#1010 (#680 item 4) renamed the "Layout flags" label on / to "Layout warnings":
- the
SourceDiagnosticsPanelsegment - the
LayoutFlagsListheading - the
LayoutFlagsListempty-state copy
The exported audit report PDF still uses the old name. src/lib/pdf/render-audit-report.ts:193 calls sectionHeading(layout, "Layout flags"), and the comment at :268 says the same.
That PR ruled this out of scope on purpose, because it is text inside an exported file and not a label on /. But the audit report is a user-facing export: it is one of the three rows in ExportDialog. So the same list of layout findings now has two names, depending on whether the user reads it on the page or in the downloaded report.
Proposed fix
Rename the audit-report section heading to "Layout warnings", and update the section comment.
Check whether any audit-report test or snapshot asserts the old string. grep -rn "Layout flags" src should then return only historical docblock references.
Acceptance criteria
- The audit-report PDF's layout section heading reads "Layout warnings".
- No user-visible "Layout flags" string remains in
src/(docblocks that record the rename history are fine). - Audit-report tests are updated and green.
Provenance: found reviewing #1010.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 4
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 66
Getting set up
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 offlinecv/OfflineCV
-
chore gaal
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
gaal improvement ux:job-search
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
All issues in offlinecv/OfflineCV
Similar issues
-
module-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
appandflow/stim#1604 · 1 comment ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 92/100
lingdojo/kana-dojo#31060 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
paperclipai/paperclip#14173 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day