ApproveParentalLinkCommandHandler silently resets InfoVault (and any unlisted permission) to false #876

New Issue

2026-07-27T14:30:27Z

spikerj commented

2026-07-27 14:30:27 +00:00

Latent bug found while designing #873. ApproveParentalLinkCommandHandler.cs:33 builds Permissions = new FeaturePermissions { Chat = true, FileUpload = true, ... } explicitly — any field not listed gets the CLR default, not the entity default. InfoVault has entity default true but ends up false after link approval. Every future permission added with a non-false default will hit the same trap.

Fix: initialize from new FeaturePermissions() and override only the intended fields (or list every field explicitly with the entity defaults), plus a pinning test.

Latent bug found while designing #873. `ApproveParentalLinkCommandHandler.cs:33` builds `Permissions = new FeaturePermissions { Chat = true, FileUpload = true, ... }` explicitly — any field not listed gets the CLR default, not the entity default. `InfoVault` has entity default `true` but ends up `false` after link approval. Every future permission added with a non-false default will hit the same trap. Fix: initialize from `new FeaturePermissions()` and override only the intended fields (or list every field explicitly with the entity defaults), plus a pinning test.

spikerj referenced this issue

2026-07-27 15:18:36 +00:00

EPIC: Sponsor family card redesign — image-backed destination tiles, achievements strip, parent-gated age #868

spikerj referenced this issue

2026-07-29 15:29:08 +00:00

exposeAgePublicly parental permission + Age on SponsorFamilyMember (consent-boundary design) #873

spikerj commented

2026-07-29 15:30:32 +00:00

Re-verified against origin/master — the bug is verbatim intact. Staying open. Recording the exact state so this isn't mistaken for fixed-by-#873:

SpikerSoft.Business/Domain/Profile/Commands/ApproveParentalLink/ApproveParentalLinkCommandHandler.cs:36-46:

childProfile.ParentalControls.Permissions = new FeaturePermissions
{
    Chat = true, FileUpload = true, VideoCall = false, PublicProfile = false,
    SocialFeatures = true, MaxDailyScreenTimeMinutes = 120,
    ExposeAgePublicly = false,
};

InfoVault is not listed, and its entity default is true (ProfileParentalSubDocuments.cs, [JsonProperty("infoVault")] public bool InfoVault { get; set; } = true;) — so link approval still silently flips it to false. The handler even carries a NOTE at :33-35 naming this ticket as open.

Important: the ExposeAgePublicly = false line at :45 was added by #873 and satisfies that ticket's item 9 only. It does not fix this one — it's another hardcoded field in the same wholesale replacement, which is the defect. Any future permission added to FeaturePermissions will be silently zeroed here too.

Remaining work: rebuild from new FeaturePermissions() and override only the fields this flow genuinely intends to set (or enumerate every field with its entity default), plus a pinning test — there is currently no test asserting unlisted permissions survive link approval, which is why this survived #873's review.

Re-verified against `origin/master` — **the bug is verbatim intact.** Staying open. Recording the exact state so this isn't mistaken for fixed-by-#873: `SpikerSoft.Business/Domain/Profile/Commands/ApproveParentalLink/ApproveParentalLinkCommandHandler.cs:36-46`: ```csharp childProfile.ParentalControls.Permissions = new FeaturePermissions { Chat = true, FileUpload = true, VideoCall = false, PublicProfile = false, SocialFeatures = true, MaxDailyScreenTimeMinutes = 120, ExposeAgePublicly = false, }; ``` `InfoVault` is not listed, and its entity default is `true` (`ProfileParentalSubDocuments.cs`, `[JsonProperty("infoVault")] public bool InfoVault { get; set; } = true;`) — so link approval still silently flips it to false. The handler even carries a NOTE at `:33-35` naming this ticket as open. **Important:** the `ExposeAgePublicly = false` line at `:45` was added by #873 and satisfies *that* ticket's item 9 only. It does not fix this one — it's another hardcoded field in the same wholesale replacement, which is the defect. Any future permission added to `FeaturePermissions` will be silently zeroed here too. Remaining work: rebuild from `new FeaturePermissions()` and override only the fields this flow genuinely intends to set (or enumerate every field with its entity default), plus a pinning test — there is currently no test asserting unlisted permissions survive link approval, which is why this survived #873's review.

spikerj referenced this issue

2026-07-29 15:30:46 +00:00

EPIC: Sponsor family card redesign — image-backed destination tiles, achievements strip, parent-gated age #868

spikerj referenced this issue

2026-07-29 16:56:19 +00:00

[Feature][Calendar] Create-for-child from the parent calendar — owner selector in the event modal (follow-up to #788) #790

spikerj referenced this issue

2026-07-29 18:25:11 +00:00

Epic: build the full parent-approval book model (upload approval chain, ApprovedBy audit, parent family/staff-uploads view, auto-Public-on-approval) #621

Sign in to join this conversation.