@tailor-platform/sdk 1.2.5 → 1.3.0

package/docs/services/staticwebsite.md

@@ -16,6 +16,12 @@ For the official Tailor Platform documentation, see [Static Website Guide](https
 
 Configure static website hosting using `defineStaticWebSite()`:
 
+**Definition Rules:**
+
+- **Multiple websites allowed**: You can define multiple static websites in your config file
+- **Configuration location**: Define in `tailor.config.ts` and add to the `staticWebsites` array
+- **Uniqueness**: Website names must be unique across all static websites
+
 ```typescript
 import { defineStaticWebSite, defineConfig } from "@tailor-platform/sdk";
 
@@ -23,8 +29,13 @@ const website = defineStaticWebSite("my-website", {
   description: "My Static Website",
 });
 
+// You can define multiple static websites
+const adminWebsite = defineStaticWebSite("admin-website", {
+  description: "Admin Dashboard",
+});
+
 export default defineConfig({
-  staticWebsites: [website],
+  staticWebsites: [website, adminWebsite], // Add all websites to the array
 });
 ```
 

package/docs/services/tailordb.md

@@ -18,15 +18,30 @@ For the official Tailor Platform documentation, see [TailorDB Guide](https://doc
 
 Define TailorDB Types in files matching glob patterns specified in `tailor.config.ts`.
 
+**Definition Rules:**
+
+- **Multiple types per file**: You can define multiple TailorDB types in a single file
+- **Export method**: Use named exports (`export const`)
+- **Export both value and type**: Always export both the runtime value and TypeScript type
+- **Uniqueness**: Type names must be unique across all TailorDB files
+
 ```typescript
 import { db } from "@tailor-platform/sdk";
 
+// Export both value and type
 export const user = db.type("User", {
   name: db.string(),
   email: db.string().unique(),
   age: db.int(),
   ...db.fields.timestamps(),
 });
+export type user = typeof user;
+
+// You can define multiple types in the same file
+export const role = db.type("Role", {
+  name: db.string().unique(),
+});
+export type role = typeof role;
 ```
 
 Specify plural form by passing an array as first argument:
@@ -190,26 +205,130 @@ type User {
 
 ### Hooks
 
-Add hooks to execute functions during data creation or update:
+Add hooks to execute functions during data creation or update. Hooks receive three arguments:
+
+- `value`: User input if provided, otherwise existing value on update or null on create
+- `data`: Entire record data (for accessing other field values)
+- `user`: User performing the operation
+
+#### Field-level Hooks
+
+Set hooks directly on individual fields:
 
 ```typescript
-db.datetime().hooks({
-  create: () => new Date(),
-  update: () => new Date(),
+db.string().hooks({
+  create: ({ user }) => user.id,
+  update: ({ value }) => value,
 });
 ```
 
-Function arguments include: `value` (field value), `data` (entire record value), `user` (user performing the operation).
+**Note:** When setting hooks at the field level, the `data` argument type is `unknown` since the field doesn't know about other fields in the type. Use type-level hooks if you need to access other fields with type safety.
+
+#### Type-level Hooks
+
+Set hooks for multiple fields at once using `db.type().hooks()`:
+
+```typescript
+export const customer = db
+  .type("Customer", {
+    firstName: db.string(),
+    lastName: db.string(),
+    fullName: db.string(),
+  })
+  .hooks({
+    fullName: {
+      create: ({ data }) => `${data.firstName} ${data.lastName}`,
+      update: ({ data }) => `${data.firstName} ${data.lastName}`,
+    },
+  });
+```
+
+**⚠️ Important:** Field-level and type-level hooks cannot coexist on the same field. TypeScript will prevent this at compile time:
+
+```typescript
+// ❌ Compile error - cannot set hooks on the same field twice
+export const user = db
+  .type("User", {
+    name: db.string().hooks({ create: ({ data }) => data.firstName }), // Field-level
+  })
+  .hooks({
+    name: { create: ({ data }) => data.lastName }, // Type-level - ERROR
+  });
+
+// ✅ Correct - set hooks on different fields
+export const user = db
+  .type("User", {
+    firstName: db.string().hooks({ create: () => "John" }), // Field-level on firstName
+    lastName: db.string(),
+  })
+  .hooks({
+    lastName: { create: () => "Doe" }, // Type-level on lastName
+  });
+```
 
 ### Validation
 
+Add validation rules to fields. Validators receive three arguments (executed after hooks):
+
+- `value`: Field value after hook transformation
+- `data`: Entire record data after hook transformations (for accessing other field values)
+- `user`: User performing the operation
+
+Validators return `true` for success, `false` for failure. Use array form `[validator, errorMessage]` for custom error messages.
+
+#### Field-level Validation
+
+Set validators directly on individual fields:
+
 ```typescript
 db.string().validate(
-  ({ value }) => value.length > 5,
-  [({ value }) => value.length < 10, "Value must be shorter than 10 characters"],
+  ({ value }) => value.includes("@"),
+  [({ value }) => value.length >= 5, "Email must be at least 5 characters"],
 );
 ```
 
+#### Type-level Validation
+
+Set validators for multiple fields at once using `db.type().validate()`:
+
+```typescript
+export const user = db
+  .type("User", {
+    name: db.string(),
+    email: db.string(),
+  })
+  .validate({
+    name: [({ value }) => value.length > 5, "Name must be longer than 5 characters"],
+    email: [
+      ({ value }) => value.includes("@"),
+      [({ value }) => value.length >= 5, "Email must be at least 5 characters"],
+    ],
+  });
+```
+
+**⚠️ Important:** Field-level and type-level validation cannot coexist on the same field. TypeScript will prevent this at compile time:
+
+```typescript
+// ❌ Compile error - cannot set validation on the same field twice
+export const user = db
+  .type("User", {
+    name: db.string().validate(({ value }) => value.length > 0), // Field-level
+  })
+  .validate({
+    name: [({ value }) => value.length < 100, "Too long"], // Type-level - ERROR
+  });
+
+// ✅ Correct - set validation on different fields
+export const user = db
+  .type("User", {
+    name: db.string().validate(({ value }) => value.length > 0), // Field-level on name
+    email: db.string(),
+  })
+  .validate({
+    email: [({ value }) => value.includes("@"), "Invalid email"], // Type-level on email
+  });
+```
+
 ### Vector Search
 
 ```typescript

package/docs/services/workflow.md

@@ -18,6 +18,14 @@ For the official Tailor Platform documentation, see [Workflow Guide](https://doc
 
 All workflow components must follow these rules:
 
+**Definition Rules:**
+
+- **One workflow + multiple jobs per file**: Each file can define multiple jobs (named exports) and one workflow (default export)
+- **Workflow export method**: Must use `export default`
+- **Job export method**: Must use named exports (`export const`)
+- **Job name uniqueness**: Job names must be unique across the entire project (not just within one file)
+- **mainJob required**: Every workflow must specify a `mainJob`
+
 | Rule                                           | Description                                                                                              |
 | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
 | `createWorkflow` result must be default export | Workflow files must export the workflow as default                                                       |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/sdk",
-  "version": "1.2.5",
+  "version": "1.3.0",
   "description": "Tailor Platform SDK - The SDK to work with Tailor Platform",
   "license": "MIT",
   "repository": {
@@ -43,7 +43,7 @@
     "@bufbuild/protobuf": "2.10.2",
     "@connectrpc/connect": "2.1.1",
     "@connectrpc/connect-node": "2.1.1",
-    "@oxc-project/types": "0.107.0",
+    "@oxc-project/types": "0.108.0",
     "@standard-schema/spec": "1.1.0",
     "@urql/core": "6.0.1",
     "chalk": "5.6.2",
@@ -59,15 +59,16 @@
     "multiline-ts": "4.0.1",
     "open": "11.0.0",
     "ora": "9.0.0",
-    "oxc-parser": "0.107.0",
+    "oxc-parser": "0.108.0",
     "p-limit": "7.2.0",
+    "pathe": "2.0.3",
     "pkg-types": "2.3.0",
-    "rolldown": "1.0.0-beta.59",
+    "rolldown": "1.0.0-beta.60",
     "std-env": "3.10.0",
     "table": "6.9.0",
     "ts-cron-validator": "1.1.5",
     "tsx": "4.21.0",
-    "type-fest": "5.3.1",
+    "type-fest": "5.4.1",
     "xdg-basedir": "5.1.0",
     "zod": "4.3.5"
   },
@@ -77,21 +78,33 @@
     "@toiroakr/lines-db": "0.6.1",
     "@types/madge": "5.0.3",
     "@types/mime-types": "3.0.1",
-    "@types/node": "24.10.7",
-    "@typescript/native-preview": "7.0.0-dev.20260111.1",
-    "@vitest/coverage-v8": "4.0.16",
+    "@types/node": "24.10.9",
+    "@typescript/native-preview": "7.0.0-dev.20260116.1",
+    "@vitest/coverage-v8": "4.0.17",
     "cross-env": "10.1.0",
     "eslint": "9.39.2",
     "eslint-plugin-jsdoc": "62.0.0",
-    "eslint-plugin-oxlint": "1.38.0",
+    "eslint-plugin-oxlint": "1.39.0",
     "globals": "17.0.0",
-    "oxlint": "1.38.0",
-    "oxlint-tsgolint": "0.11.0",
+    "oxlint": "1.39.0",
+    "oxlint-tsgolint": "0.11.1",
     "sonda": "0.10.1",
     "tsdown": "0.19.0",
     "typescript": "5.9.3",
-    "typescript-eslint": "8.52.0",
-    "vitest": "4.0.16"
+    "typescript-eslint": "8.53.0",
+    "vitest": "4.0.17"
+  },
+  "peerDependencies": {
+    "@liam-hq/cli": "*",
+    "serve": "*"
+  },
+  "peerDependenciesMeta": {
+    "@liam-hq/cli": {
+      "optional": true
+    },
+    "serve": {
+      "optional": true
+    }
   },
   "scripts": {
     "test": "vitest",