mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 15:23:29 +00:00
docs(sharing): the booster needs two sections, and the guide promised it at one level
The write-level row listed "a vaccination dose and the booster reminder it suggests" three paragraphs under a section table that puts the vaccination record in Health background. Read together, that tells a self-hoster a health-background WRITE grant can plan a booster — which the route beside it now refuses, because the reminder it mints lives under Readings. The row lists the dose alone, and the exceptions paragraph, which is where a reader looks for exactly this, carries the two-section case and says the dose logs either way. With it, the small things the same pass turned up: The cycle-insights fixture asserted a property it could not show. Its docblock claims the cycle-native answer survives the fence, and it seeded no symptom at all, so `symptomPatterns` was empty in every leg and a regression that emptied it along with the foreign columns would have passed green. One catalogue symptom on the luteal days, asserted on the owner leg and on the cycle-only one. The immunization rows matched on a bare `role="button"`, which passes vacuously the day the card becomes a real button and fails for the wrong reason if anything else in the subtree grows one. They carry the same stable marker the visit card took. `/api/cycle/calendar` reads the same wrist-temperature channel the crosstab does and is deliberately not fenced, and it was the only one of the pair with nothing saying why: no value from it reaches the response. The encrypted export's new 403 documented the switch refusal and not the narrow-scope one it answers first, unlike the two settings operations beside it. Both sheets say at the top that their Save and Delete are gated at the caller, so a third mount reads the constraint before it violates it. And one docblock line ran past the wrap.
This commit is contained in:
1 parent
681e69a723
commit
83b7cd223a
10 files changed
+111
-18
No files matched your search
@@ -20,6 +20,16 @@
|
||||
* saved and a plain sentence saying the checkup stayed open. That is reported
|
||||
* rather than skipped in silence: somebody who believes a checkup was closed
|
||||
* will not look at it again.
|
||||
*
|
||||
* Capability note: this sheet carries no capability check of its own, by
|
||||
* decision. Save is a create on one mount and an edit on the other, and Delete
|
||||
* exists only in edit mode — so the question belongs to whoever opens it.
|
||||
* `VisitsSection` hands it a record only under `canManageDomain("profile")`,
|
||||
* and the two mounts that can only create (`EpisodeVisitsCard`,
|
||||
* `VorsorgeSection`) pass `encounter={null}` behind their own write check. A
|
||||
* THIRD mount that hands this sheet a record without asking the manage
|
||||
* question reintroduces an ungated Delete, and nothing here will fail. Ask at
|
||||
* the caller, or move the check in here for everyone.
|
||||
*/
|
||||
import { useState } from "react";
|
||||
import { Trash2 } from "lucide-react";
|
||||
|
||||
Reference in new issue
Block a user