spikerj/spikersoft-issues
1
0
Fork 0
Code Issues 196 Pull Requests Actions Packages Projects Releases Wiki Activity

ProfileMapper.ToDto omits 5 permission fields — child's own blogPosting etc. always read as defaults #759

New Issue
Closed
opened 2026-07-21 02:59:47 +00:00 by spikerj · 1 comment
spikerj commented 2026-07-21 02:59:47 +00:00
Owner
Copy Link
Copy Source

Latent backend bug spotted during the #735 minor-map investigation and never filed (it sat only in session notes).

ProfileMapper.ToDto (spikersoft-backend) does not map five of the FeaturePermissions fields — blogPosting among them — so a child's own profile DTO always carries the default values for those permissions regardless of what's stored. The #735 fix addressed the parent-map masking; this is the remaining mapper gap on the child's own view.

Repro sketch: grant a child blogPosting via the parent flow, fetch the child's own profile → DTO shows the default, not the granted value.

Fix: add the missing fields to ToDto and a mapper round-trip test asserting every FeaturePermissions member survives (that test would have caught this class of omission).

Latent backend bug spotted during the #735 minor-map investigation and never filed (it sat only in session notes). `ProfileMapper.ToDto` (spikersoft-backend) does not map five of the `FeaturePermissions` fields — `blogPosting` among them — so a child's *own* profile DTO always carries the default values for those permissions regardless of what's stored. The #735 fix addressed the parent-map masking; this is the remaining mapper gap on the child's own view. Repro sketch: grant a child blogPosting via the parent flow, fetch the child's own profile → DTO shows the default, not the granted value. Fix: add the missing fields to `ToDto` and a mapper round-trip test asserting every `FeaturePermissions` member survives (that test would have caught this class of omission).
spikerj commented 2026-07-21 03:00:40 +00:00
Author
Owner
Copy Link
Copy Source

Duplicate — filed from a stale note. This was already tracked as #736 and fixed in backend PR #435 (all 13 FeaturePermissions fields mapped + a 13-field pin test), merged 2026-07-20. Closing.

Duplicate — filed from a stale note. This was already tracked as #736 and fixed in backend PR #435 (all 13 FeaturePermissions fields mapped + a 13-field pin test), merged 2026-07-20. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#759