Follow-up from the #102 in-app editor (PR #104), flagged in the overnight report as a known first-pass limitation.
Behavior: in SidecarEditorDialog, changing the section combo re-reads the pick-lists from the raw text for the newly-selected section and resets the "changed since load" baseline. So pick-list edits made in section A, then abandoned by switching to section B before Save, are silently dropped. The raw editor remains the source of truth, so nothing is corrupted — but a user can lose form edits without warning.
Options when picking this up:
Apply the current section's pending form changes into the raw text before switching (so they persist across a section switch), or
Warn/confirm on switch when the form has unsaved changes, or
Make the form edits write through to raw immediately (no separate baseline).
Low priority (P2) — documented, no data loss. Part of epic #94; scoped out of #102's first pass.
Follow-up from the #102 in-app editor (PR #104), flagged in the overnight report as a known first-pass limitation.
**Behavior:** in `SidecarEditorDialog`, changing the section combo re-reads the pick-lists from the raw text for the newly-selected section and resets the "changed since load" baseline. So pick-list edits made in section A, then abandoned by switching to section B *before Save*, are silently dropped. The raw editor remains the source of truth, so nothing is corrupted — but a user can lose form edits without warning.
**Options when picking this up:**
- Apply the current section's pending form changes into the raw text *before* switching (so they persist across a section switch), or
- Warn/confirm on switch when the form has unsaved changes, or
- Make the form edits write through to raw immediately (no separate baseline).
Low priority (P2) — documented, no data loss. Part of epic #94; scoped out of #102's first pass.
the_og
added the P2 label 2026-08-13 00:42:05 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up from the #102 in-app editor (PR #104), flagged in the overnight report as a known first-pass limitation.
Behavior: in
SidecarEditorDialog, changing the section combo re-reads the pick-lists from the raw text for the newly-selected section and resets the "changed since load" baseline. So pick-list edits made in section A, then abandoned by switching to section B before Save, are silently dropped. The raw editor remains the source of truth, so nothing is corrupted — but a user can lose form edits without warning.Options when picking this up:
Low priority (P2) — documented, no data loss. Part of epic #94; scoped out of #102's first pass.