Motif: edit a Proposal's Rationale in the rich field
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with blocker #132 and the existing Proposals page, then trace the rationale command and shared rich field it uses. Implement and test viewing, editing, saving, canceling, findings, refused saves, history restore, and the decided-state freeze in the headless App tests. Done when those tests pass and the release surface follows the existing Proposals page, including checking whether the field is gated.
Written by the indexing model from the issue text.
Description
Parent
#74 · ADR 0099
What to build
On the Proposals page the Rationale is shown rendered in the shared rich field (links open their object) instead of plain text. For an open Proposal, "Edit" makes it editable; Save writes through the rationale command (findings shown under the field; on Ready, a refused Save keeps the person's text in the field with the findings); Cancel discards. "Restore an earlier version" offers the kept history before the Proposal is decided. Frozen when decided.
Acceptance criteria
- Headless App tests: view, Edit/Save/Cancel, findings shown, Ready refusal keeps the text, restore earlier version, frozen when decided
- Release surface follows the existing Proposals page (no preview gate needed unless the field is still gated: say which)
Blocked by
- #132
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- Avg merge
- 3h 55m
- Merged PRs (30d)
- 36
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 sillsdev/motif
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
Playground selection bar: comes back after Apply or scrolling while focus is in the Markdown paneOpentextediting
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
textediting
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
textediting
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
textediting
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
bug emitter:client:csharp
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/typespec#12572 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
AWS Lambda: KeyNotFoundException drops HTTP-triggered transactions when allowAllHeaders is disabledOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
newrelic/newrelic-dotnet-agent#3949 · 1 comment ·
Maintainers usually reply within 1 day
-
area-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/aspnetcore#70545 · 1 comment ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100