Issue lists must also show the icon for open/closed #30

Closed
opened 2026-07-31 14:31:24 +00:00 by hugo · 1 comment
Owner

Issues in lists should also show the icon, because they can be mixed like the issues linked to a milestone.

Issues in lists should also show the icon, because they can be mixed like the issues linked to a milestone.
hugo added this to the first feature complete release milestone 2026-07-31 14:31:24 +00:00
hugo added the bug label 2026-07-31 14:31:24 +00:00
Author
Owner

Implemented in e39695f.

  • Added issue state to the Rust-owned IssueRow presentation record so every issue-list surface receives view-ready state.
  • Added shared native SF Symbol rendering for green open and purple closed states in repository issue lists and milestone issue lists, including VoiceOver labels and compression-safe Dynamic Type layout.
  • Regenerated the UniFFI Swift binding and updated TESTING.md for both affected list contexts.

Verified in isolation with the full required gate suite (cargo fmt, warning-free workspace check, Clippy with warnings denied, and all workspace tests), a signed arm64 iPhone 17 Pro simulator build, and manual simulator checks of open, closed, and milestone issue rows plus their accessibility labels.

Implemented in e39695f. - Added issue state to the Rust-owned `IssueRow` presentation record so every issue-list surface receives view-ready state. - Added shared native SF Symbol rendering for green open and purple closed states in repository issue lists and milestone issue lists, including VoiceOver labels and compression-safe Dynamic Type layout. - Regenerated the UniFFI Swift binding and updated `TESTING.md` for both affected list contexts. Verified in isolation with the full required gate suite (`cargo fmt`, warning-free workspace check, Clippy with warnings denied, and all workspace tests), a signed arm64 iPhone 17 Pro simulator build, and manual simulator checks of open, closed, and milestone issue rows plus their accessibility labels.
hugo closed this issue 2026-07-31 15:08:02 +00:00
Sign in to join this conversation.