hugo/Gotcha
1
0
Fork 0
Code Issues 13 Pull Requests Actions Packages Projects Releases Wiki Activity

the issue state (open/closed) must be shown beside the title #18

New Issue
Closed
opened 2026-07-31 10:21:59 +00:00 by hugo · 1 comment
hugo commented 2026-07-31 10:21:59 +00:00
Owner
Copy Link

since users can end up on an issue from different places, it is imperative that the state of the issue is shown beside the title, so that the user knows they are looking at an open or closed item. it can be an icon that denotes the state.

since users can end up on an issue from different places, it is imperative that the state of the issue is shown beside the title, so that the user knows they are looking at an open or closed item. it can be an icon that denotes the state.
hugo added this to the first feature complete release milestone 2026-07-31 10:21:59 +00:00
hugo added the bug label 2026-07-31 10:21:59 +00:00
hugo commented 2026-07-31 10:59:30 +00:00
Author
Owner
Copy Link

Implemented in 6374636. Issue details now preserve the Gitea state through the Rust presentation model and UniFFI bridge, then show a Dynamic Type-aware SF Symbol beside the title: green for open, purple for closed, with explicit VoiceOver labels and a safe unknown-state fallback. Updated TESTING.md with the open/closed regression scenario. Verified in isolation with cargo fmt --all -- --check, warning-free cargo check, Clippy with -D warnings, the full workspace test suite, and a signed arm64 iPhone 17 Pro / iOS 26.5 simulator build. Installed and launched the app; visually verified open and closed issue details at default and Accessibility Large text sizes and confirmed the accessibility tree announces both states.

Implemented in 6374636. Issue details now preserve the Gitea state through the Rust presentation model and UniFFI bridge, then show a Dynamic Type-aware SF Symbol beside the title: green for open, purple for closed, with explicit VoiceOver labels and a safe unknown-state fallback. Updated TESTING.md with the open/closed regression scenario. Verified in isolation with cargo fmt --all -- --check, warning-free cargo check, Clippy with -D warnings, the full workspace test suite, and a signed arm64 iPhone 17 Pro / iOS 26.5 simulator build. Installed and launched the app; visually verified open and closed issue details at default and Accessibility Large text sizes and confirmed the accessibility tree announces both states.
hugo closed this issue 2026-07-31 10:59:36 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 critical
critical issues that take precendence over others of the same grouping
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 idea
an idea for a future milestone
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label bug
Milestone
No items
No Milestone first feature complete release
Projects
Clear projects
No project
Assignees
Clear assignees
hugo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hugo/Gotcha#18
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?