Skip to content

Commit b29eaa1

Browse files
committed
test(stack-supabase): assert the ciphertext error log carries the failure kind
main's plaintext-table test (from the CIP-5151 fix) expected the error log to carry the row path "[0].meta". This branch stops logging the error message at all (CIP-5161), so the log now names the failure kind (DecryptionError) instead. The assertion that matters, that the jsonb key never reaches the log, still holds; the path is still in the error returned to the caller. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Jmn7pT73uHWFP7RKEikuh
1 parent d61bfd4 commit b29eaa1

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎languages/typescript/packages/stack-supabase/__tests__/supabase-plaintext-table.test.ts‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -262,10 +262,11 @@ describe('plaintext table rows that carry ciphertext', () => {
262262

263263
expect(error?.message).toContain('"[0].meta"')
264264
expect(error?.message).not.toContain('ssn-078-05-1120')
265-
// The message reaches the logger too, so the log must not carry it either.
265+
// The log names the failure's kind, never the message (CIP-5161), so it
266+
// carries neither the key nor the row path.
266267
expect(logged).toHaveBeenCalled()
267268
for (const args of logged.mock.calls) {
268-
expect(args.join(' ')).toContain('"[0].meta"')
269+
expect(args.join(' ')).toContain('DecryptionError')
269270
expect(args.join(' ')).not.toContain('ssn-078-05-1120')
270271
}
271272
} finally {

0 commit comments

Comments
 (0)