Skip to content

Commit 46c61da

Browse files
committed
test(plugin-auth): say plainly why the null-role fixture is written beneath the engine
Claude-Session: https://claude.ai/code/session_01UnHcTADjeg3VwxF21QHj7W Co-authored-by: Claude <noreply@anthropic.com>
1 parent 5db01d5 commit 46c61da

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎packages/plugins/plugin-auth/src/organization-delete-read-fault.test.ts‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -126,8 +126,9 @@ async function ownerOfTarget(role: string | null = 'owner') {
126126
const active = await post(manager, '/organization/set-active', { organizationId: TARGET }, cookie);
127127
expect(active.status, await active.clone().text()).toBe(200);
128128
if (role !== 'owner') {
129-
// Below the engine, which would apply the field's default to a null: the
130-
// row as a store can hold it.
129+
// Written beneath the engine, so the row is exactly what a store can hold
130+
// (`role` is not a required column), whatever the engine's write path does
131+
// with a null.
131132
await (engine as any).getDriver('sys_member').update('sys_member', 'mem_owner', { role });
132133
}
133134
return { engine, manager, cookie };

0 commit comments

Comments
 (0)