chore(stack): disable logging by default

Author: calvinbrewer

docs/reference/configuration.md

@@ -142,7 +142,11 @@ Each keyset provides an isolated set of encryption keys, so data encrypted under
 
 ### Logging configuration
 
-You can configure structured logging for the Encryption client:
+Logging is disabled by default. You can enable it by setting the `STASH_LOG_LEVEL` environment variable or by configuring it programmatically:
+
+```bash
+STASH_LOG_LEVEL=debug  # debug | info | warn | error
+```
 
 ```ts
 const client = await Encryption({
@@ -160,7 +164,7 @@ const client = await Encryption({
 
 | Option | Type | Default | Description |
 |--------|------|---------|-------------|
-| `enabled` | `boolean` | `true` | Toggle logging on or off. |
+| `enabled` | `boolean` | `false` | Toggle logging on or off. Automatically enabled when `STASH_LOG_LEVEL` is set. |
 | `pretty` | `boolean` | Auto-detected | Enable pretty-printed log format. |
 | `drain` | `(ctx) => void` | `undefined` | Callback for forwarding log events to an external platform. |
 

docs/reference/dynamodb.md

@@ -171,17 +171,17 @@ const decryptedUsers = decryptedResult.data
 
 ## Using nested objects
 
-The DynamoDB helper supports nested object encryption using `encryptedValue`:
+The DynamoDB helper supports nested object encryption using `encryptedField`:
 
 ```typescript
-import { encryptedTable, encryptedColumn, encryptedValue } from '@cipherstash/stack/schema'
+import { encryptedTable, encryptedColumn, encryptedField } from '@cipherstash/stack/schema'
 
 const users = encryptedTable('users', {
   email: encryptedColumn('email'),
   profile: {
-    name: encryptedValue('profile.name'),
+    name: encryptedField('profile.name'),
     address: {
-      street: encryptedValue('profile.address.street'),
+      street: encryptedField('profile.address.street'),
     },
   },
 })

docs/reference/schema.md

@@ -81,23 +81,23 @@ export const protectedUsers = encryptedTable("users", {
 CipherStash Encryption supports nested objects in your schema, allowing you to encrypt **but not search on** nested properties. You can define nested objects up to 3 levels deep.
 This is useful for data stores that have less structured data, like NoSQL databases.
 
-You can define nested objects by using the `encryptedValue` function to define a value in a nested object. The value naming convention of the `encryptedValue` function is a dot-separated string of the nested object path, e.g. `profile.name` or `profile.address.street`.
+You can define nested objects by using the `encryptedField` function to define a value in a nested object. The value naming convention of the `encryptedField` function is a dot-separated string of the nested object path, e.g. `profile.name` or `profile.address.street`.
 
 > [!NOTE]
 > Using nested objects is not recommended for SQL databases, as it will not be searchable.
 > You should either use a JSON data type and encrypt the entire object, or use a separate column for each nested property.
 
 ```ts
-import { encryptedTable, encryptedColumn, encryptedValue } from "@cipherstash/stack/schema";
+import { encryptedTable, encryptedColumn, encryptedField } from "@cipherstash/stack/schema";
 
 export const protectedUsers = encryptedTable("users", {
   email: encryptedColumn("email").freeTextSearch().equality().orderAndRange(),
   profile: {
-    name: encryptedValue("profile.name"),
+    name: encryptedField("profile.name"),
     address: {
-      street: encryptedValue("profile.address.street"),
+      street: encryptedField("profile.address.street"),
       location: {
-        coordinates: encryptedValue("profile.address.location.coordinates"),
+        coordinates: encryptedField("profile.address.location.coordinates"),
       },
     },
   },
@@ -112,8 +112,8 @@ When working with nested objects:
 - Optional nested objects are supported
 
 > [!WARNING]
-> TODO: The schema builder does not validate the values you supply to the `encryptedValue` or `encryptedColumn` functions.
-> These values are meant to be unique, and and cause unexpected behavior if they are not defined correctly.
+> TODO: The schema builder does not validate the values you supply to the `encryptedField` or `encryptedColumn` functions.
+> These values are meant to be unique, and cause unexpected behavior if they are not defined correctly.
 
 ## Data types
 

packages/stack/__tests__/drizzle-operators-jsonb.test.ts

@@ -1,4 +1,4 @@
-import type { EncryptionClient } from '@/encryption/ffi'
+import type { EncryptionClient } from '@/encryption'
 import { pgTable } from 'drizzle-orm/pg-core'
 import { PgDialect } from 'drizzle-orm/pg-core'
 import { describe, expect, it, vi } from 'vitest'

packages/stack/__tests__/encrypt-query.test.ts

@@ -1,5 +1,5 @@
 import 'dotenv/config'
-import type { EncryptionClient } from '@/encryption/ffi'
+import type { EncryptionClient } from '@/encryption'
 import { EncryptionErrorTypes } from '@/errors'
 import { Encryption } from '@/index'
 import { beforeAll, describe, expect, it } from 'vitest'

packages/stack/__tests__/error-codes.test.ts

@@ -1,5 +1,5 @@
 import 'dotenv/config'
-import type { EncryptionClient } from '@/encryption/ffi'
+import type { EncryptionClient } from '@/encryption'
 import { Encryption, EncryptionErrorTypes } from '@/index'
 import { encryptedColumn, encryptedTable } from '@/schema'
 import { ProtectError as FfiProtectError } from '@cipherstash/protect-ffi'

packages/stack/__tests__/infer-index-type.test.ts

@@ -2,7 +2,7 @@ import {
   inferIndexType,
   inferQueryOpFromPlaintext,
   validateIndexType,
-} from '@/encryption/ffi/helpers/infer-index-type'
+} from '@/encryption/helpers/infer-index-type'
 import { encryptedColumn, encryptedTable } from '@/schema'
 import { describe, expect, it } from 'vitest'
 

packages/stack/__tests__/types.test-d.ts

@@ -19,7 +19,7 @@ import type {
   OtherFields,
   QueryTypeName,
 } from '../src/types.js'
-import type { EncryptionClient } from '../src/encryption/ffi/index.js'
+import type { EncryptionClient } from '../src/encryption/index.js'
 
 describe('Type inference', () => {
   it('encryptedTable returns ProtectTable with column access', () => {

packages/stack/src/client.ts

@@ -20,4 +20,4 @@ export type {
   InferPlaintext,
   InferEncrypted,
 } from '@/schema'
-export type { EncryptionClient } from '@/encryption/ffi'
+export type { EncryptionClient } from '@/encryption'

packages/stack/src/drizzle/operators.ts

@@ -1,5 +1,9 @@
-import type { EncryptionClient } from '@/encryption/ffi'
-import type { EncryptedColumn, EncryptedTable, EncryptedTableColumn } from '@/schema'
+import type { EncryptionClient } from '@/encryption/index.js'
+import type {
+  EncryptedColumn,
+  EncryptedTable,
+  EncryptedTableColumn,
+} from '@/schema'
 import { type QueryTypeName, queryTypes } from '@/types'
 import {
   type SQL,
@@ -1170,7 +1174,8 @@ export function createEncryptionOperators(encryptionClient: EncryptionClient): {
 } {
   // Create a cache for encrypted tables keyed by table name
   const tableCache = new Map<string, EncryptedTable<EncryptedTableColumn>>()
-  const defaultTable: EncryptedTable<EncryptedTableColumn> | undefined = undefined
+  const defaultTable: EncryptedTable<EncryptedTableColumn> | undefined =
+    undefined
 
   /**
    * Equality operator - encrypts value and uses regular Drizzle operator