[IV-3BH7] Headings never show a code
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
Research direction
Read lightning/ui/templates/investments/asset_form.html:4 and lightning/ui/templates/investments/form.html:4, then review the linked naming guidance and ai/ARCHITECTURE.md. Replace the composed edit headings with the specified translated labels and subtitles; verify that grep -rn "'Edit ' ~" lightning/ui/templates returns no matches.
Written by the indexing model from the issue text.
Description
Code
IV-3BH7
What to build (One name per thing and no accounting jargon - ledger, counterparty, reevaluation, Title Case categories, three names for planning)
Files: lightning/ui/templates/investments/asset_form.html:4, lightning/ui/templates/investments/form.html:4.
Do: "Edit FND:AZMM" → "Edit {name}" with the asset's display name; "Edit OUT-…" → "Edit transaction" with the date and payee as the subtitle. One |tr key each with a value, not 'Edit ' ~ ….
Done when: grep -rn "'Edit ' ~" lightning/ui/templates is empty.
Context
Report r28 F16-F18.
Read first
3-polish-and-arabic/IV-3BH-one-name-per-thing-no-jargon.md · financial rules in ai/ARCHITECTURE.md (figures are computed in Python services, never templates).
Reward: 200 Lightning Coins once a pull request that says Closes #<this issue> is merged. To work on it: comment /take. Setup: CONTRIBUTING.md.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 364
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 LightningEg/Lightning
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
LightningEg/Lightning#591 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LightningEg/Lightning#588 ·
Maintainers usually reply within 1 day
-
can:opus pillar:reach state:ready when:someday
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
LightningEg/Lightning#576 ·
Maintainers usually reply within 1 day
-
coins:200 good first issue kind:improvement-visual pillar:feel
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LightningEg/Lightning#435 ·
Maintainers usually reply within 1 day
-
coins:200 good first issue kind:improvement-visual pillar:feel
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LightningEg/Lightning#426 ·
Maintainers usually reply within 1 day
All issues in LightningEg/Lightning
Similar issues
-
documentation good first issue priority: P2 status: ready
Difficulty 1/5 Under an hour Newbie friendliness 88/100
RhinoLink-Tech/data-fabric#500 ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2384 ·
Maintainers usually reply within 1 day
-
[Bug]: The H2 series' and the H3C's fan 3 is labelled "Chamber Fan", Bambu calls it the exhaust fanOpenarea:ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
btclib-org/btclib#3062 ·
Maintainers usually reply within 1 day
-
area:evals area:infra enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jse-avl/support-bot#4 · 1 comment ·