Skip to content

refactor(plugin-security): move SecurityPlugin's leaf readers into security-plugin-object-inputs.ts (#25223 cut 1) #25290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 2 commits into from
Oct 22, 2026
Merged

refactor(plugin-security): move SecurityPlugin's leaf readers into security-plugin-object-inputs.ts (#25223 cut 1) #25290

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7016ae1
refactor(plugin-security): move SecurityPlugin's leaf readers into se…
claude Oct 22, 2026
a7cd7c6
test(plugin-security): say why the raw registration door alone pins t…
claude Oct 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions packages/plugins/plugin-security/src/controlled-by-parent-unwritable-master-write.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,13 @@
* - every insert, single or batch, whether or not its body names a master;
* - every update whose body carries the reference key, a master or `null`.
*
* Why the raw door alone pins it (ruling 6345869077 item 6): the three doors
* that skip the parse — `defineStack` with `strict: false`, plugin code's raw
* `registerApp` / `registerObject`, and an 18.0.0-era `sys_metadata` row the
* boot registers under `[metadata_spec_invalid]` — all end in the one
* `SchemaRegistry` entry the gate's resolver reads through `ql.getSchema()`,
* so a declaration from any of them reaches the gate in the same form.
*
* One rule for both flags, for a member and for a platform admin alike, on an
* ordinary object and on a `sys_`-named one (which the engine treats
* differently on insert — the rule does not). What stays as it was:
Expand Down
Loading
Loading