Skip to content

Fix/exposed value view delete record#1302

Merged
mstijak merged 2 commits into
masterfrom
fix/exposed-value-view-delete-record
Jun 18, 2026
Merged

Fix/exposed value view delete record#1302
mstijak merged 2 commits into
masterfrom
fix/exposed-value-view-delete-record

Conversation

@nebojsa-peric

Copy link
Copy Markdown
Collaborator

No description provided.

Adds a spec mirroring how Sandbox wires ExposedValueView (a storage object
keyed by a slot key, exposed to children under a record name). Includes a
case for deleting the entire exposed record, which currently fails:
deleteItem guards on container.hasOwnProperty(recordName) instead of the
slot key, so the delete is a silent no-op and the slot survives.
deleteItem guarded on container.hasOwnProperty(path) where path is the
record name (e.g. "$page"), but the container is keyed by the slot key
(this.key). The check never matched, so deleting the whole exposed record
was a silent no-op — a sandboxed page's state survived in storage and was
re-exposed on the next visit. Guard on this.key, matching setItem and the
delete below it.
@mstijak mstijak merged commit 5c19fd4 into master Jun 18, 2026
2 checks passed
@mstijak mstijak deleted the fix/exposed-value-view-delete-record branch June 18, 2026 09:31
@mstijak mstijak mentioned this pull request Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants