bleedingdeacons / monitor / 33367292453
93%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 16
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: 92.324% (-3.9%) from 96.217%
33367292453

push

github

web-flow 
feat(compose): send, reply to and pass back alerts from the handset (#36)

Hand has been a pager. It could receive an alert, alarm for it and
acknowledge it, and that was the whole of what it could do. This adds
the other direction.

New message. A compose screen addressed to one member or to one
committee, with the level and first-to-respond controls wp-admin's Send
Message screen has, and its warning about where the text ends up. There
is deliberately no "everybody": any responder can send from a handset,
and a broadcast is the loudest thing this system does - nothing a tired
thumb can reach should put the whole rota's alarms on. The server
refuses a send with no recipient rather than widening it.

The picker shows the anonymous name with the home group, because a rota
has more than one Dave and the group is what tells them apart.
Unreachable members are listed and labelled rather than hidden: somebody
who cannot find a name needs to know whether they mistyped it or that
person has no phone enrolled. Committees come as a tree, indented by
depth, each with the count of handsets the branch reaches.

The directory carries no addresses at all. A recipient is chosen by id
and resolved server-side, which is what makes a directory sitting on
every handset acceptable.

Reply. Free text back to whoever raised the alert, offered on the card
and - the case it exists for - on the history row. When another
responder answers first, Reach stops serving that message and Hand
deletes every card, so the history entry is the only thing left to reply
from. Replying settles nothing: it is not a second person taking the job
on, so an outstanding alert stays outstanding.

HasDetail now counts a repliable row, because the Reply button lives in
the expanded half and plenty of alerts are only a subject line - which
is exactly the one somebody else answered first.

Pass back. The responder who took a job and cannot do it puts it out
again to the people it came from. Confirmed... (continued)

1287 of 1394 relevant lines covered (92.32%)

1260.61 hits per line

Coverage Regressions

Lines Coverage ∆ File
59
75.28
-20.95% Services/ReachClient.cs
9
95.79
0.48% Services/AlertService.cs
8
77.55
3.08% Models/AlertHistoryEntry.cs
Jobs
ID Job ID Ran Files Coverage
1 33367292453.1 16
92.32
GitHub Action Run
Source Files on build 33367292453