bleedingdeacons / link / 34511968277
92%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 19
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 95.326% (+0.03%) from 95.294%
34511968277

push

github

web-flow 
feat: show home group and GSR standing in the member selector

* feat: let a member read a message

Until now they could not. The list rendered the body with MaxLines="3"
and TailTruncation, tapping a row only marked it read, and there was
nowhere else to go — so any message longer than three lines was
permanently cut off in the only app that displays it. Fellowship stores
the whole body and the handset already holds it decrypted; nothing was
missing but a screen.

The same change makes **reply** reachable. ComposeViewModel has always
understood replyTo and subject, and Fellowship has always accepted a
reply id, but nothing in the app ever navigated with them — the entire
path was dead code. Reply lives on the message rather than the list,
because replying to something you have not opened is not a thing anybody
does.

  * MessagePage / MessageViewModel: subject, sender, the time spelled
    out, and the body with no truncation.
  * Looked up by id rather than handed the record. Shell can carry an
    object, but Android recreates the page after reclaiming a
    backgrounded process, and a detail screen that came back blank would
    be a bug nobody could reproduce on demand.
  * OpenAsync navigates whether or not the message was already read. Its
    early return on IsRead is why a second tap on a message used to do
    nothing at all.
  * Shell.TabBarIsVisible="False" on both pushed pages. The tabs stayed
    on screen while reading, which reads as a fourth tab rather than
    somewhere you came into and back out of; both platforms treat a
    detail screen as taking over.

Verified on a handset rather than by inspection: list, tap, read, back,
and the row is no longer bold. Screenshots in the PR.

Two things found on the way and not fixed here. Label has no text
selection property in MAUI 10 — I tried IsTextSelectionEnabled, which
does not exist — so a member cannot copy a number out of a message. And
that mistake reached the device: it built clean ... (continued)

1081 of 1134 relevant lines covered (95.33%)

13.58 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
98.21
-0.21% Services/FellowshipClient.cs
1
94.44
6.94% Models/DirectoryEntry.cs
Jobs
ID Job ID Ran Files Coverage
1 34511968277.1 19
95.33
GitHub Action Run
Source Files on build 34511968277