@famgia/omnify 1.0.123 → 1.0.125

package/ai-guides/schema-guide.md

@@ -1083,6 +1083,101 @@ status:
   default: draft           # Default value from enum
 ```
 
+## Partial Schema (Schema Extensions)
+
+Partial schemas allow packages to extend existing schemas with additional properties.
+This is useful when Laravel packages need to add fields to core models like User.
+
+### Basic Structure
+
+```yaml
+# schemas/billing/UserBilling.yaml
+kind: partial
+target: User  # Which schema to extend
+
+displayName:
+  ja: ユーザー請求情報
+  en: User Billing
+
+properties:
+  stripe_customer_id:
+    type: String
+    length: 255
+    nullable: true
+    displayName:
+      ja: Stripe顧客ID
+      en: Stripe Customer ID
+
+  subscription_status:
+    type: String
+    length: 50
+    nullable: true
+    displayName:
+      ja: 購読状態
+      en: Subscription Status
+```
+
+### How It Works
+
+1. **Merging**: Properties from partial schemas are merged into the target schema
+2. **Priority**: Target schema properties take priority (won't be overwritten)
+3. **Migrations**: New columns are added via ALTER TABLE migrations
+4. **Models**: TypeScript types and Laravel models include merged properties
+
+### Rules for Partial Schemas
+
+| Rule | Description |
+|------|-------------|
+| `kind: partial` | Required to mark as partial schema |
+| `target: SchemaName` | Required - specifies which schema to extend |
+| `properties` | Required - at least one property |
+| `options` | ❌ Not allowed (table options belong to target) |
+| `values` | ❌ Not allowed (that's for enums) |
+
+### Use Cases
+
+```yaml
+# Package: Billing
+kind: partial
+target: User
+properties:
+  stripe_id: { type: String, nullable: true }
+  plan: { type: String, nullable: true }
+
+# Package: Notifications
+kind: partial
+target: User
+properties:
+  notification_preferences: { type: Json, nullable: true }
+  push_token: { type: String, nullable: true }
+
+# Package: Social
+kind: partial
+target: User
+properties:
+  avatar_url: { type: String, nullable: true }
+  bio: { type: Text, nullable: true }
+```
+
+### Package Schema Registration
+
+Laravel packages can register their schema directories:
+
+```php
+// In your package's ServiceProvider
+use App\Support\Omnify;
+
+public function boot()
+{
+    Omnify::addSchemaPath(__DIR__.'/../database/schemas');
+}
+```
+
+Then run:
+```bash
+npx omnify generate
+```
+
 ## MCP Tools
 
 If Omnify MCP is configured, these tools are available:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@famgia/omnify",
-  "version": "1.0.123",
+  "version": "1.0.125",
   "description": "Schema-driven database migration system with TypeScript types and Laravel migrations",
   "type": "module",
   "main": "./dist/index.js",
@@ -26,14 +26,14 @@
     "README.md"
   ],
   "dependencies": {
-    "@famgia/omnify-cli": "0.0.119",
-    "@famgia/omnify-core": "0.0.113",
-    "@famgia/omnify-types": "0.0.111",
-    "@famgia/omnify-typescript": "0.0.101",
-    "@famgia/omnify-atlas": "0.0.107",
-    "@famgia/omnify-laravel": "0.0.122",
-    "@famgia/omnify-mcp": "0.0.99",
-    "@famgia/omnify-japan": "0.0.106"
+    "@famgia/omnify-core": "0.0.115",
+    "@famgia/omnify-types": "0.0.113",
+    "@famgia/omnify-cli": "0.0.121",
+    "@famgia/omnify-atlas": "0.0.109",
+    "@famgia/omnify-typescript": "0.0.103",
+    "@famgia/omnify-mcp": "0.0.101",
+    "@famgia/omnify-japan": "0.0.108",
+    "@famgia/omnify-laravel": "0.0.124"
   },
   "keywords": [
     "omnify",