prisma-effect-schema-generator 0.1.3 → 0.1.4

package/README.md

@@ -89,7 +89,7 @@ updated) on every regeneration.
 | `dateAs`              | `"DateFromSelf"`     | `"Date"` (ISO-string codec) or `"DateFromSelf"` (accepts native `Date`).                                          |
 | `exportModelNames`    | `"true"`             | Emit `export const ALL_MODEL_NAMES = [...] as const`.                                                             |
 | `exportModelNameType` | `"true"`             | Emit `export type ModelName = "X" | "Y"`.                                                                          |
-| `standardSchemaV1`    | `"false"`            | Wrap every model/relation schema in `Schema.standardSchemaV1(...)` for Standard Schema compatibility.          |
+| `standardSchemaV1`    | `"false"`            | Wrap schemas in `Schema.standardSchemaV1(...)`. Narrows `Context` to `never` so libraries like TanStack DB accept the schema directly. |
 | `relationColumns`     | `"false"`            | Emit a separate `Schema.Struct` for each relation that has explicit local foreign-key columns.                   |
 | `idColumn`            | `"false"`            | Emit `PRIMARY_KEY_COLUMNS` map from model name to primary-key column (or `null`).                                |
 | `softDeleteColumn`    | `"false"`            | Emit `SOFT_DELETE_COLUMNS` map from model name to detected soft-delete column.                                   |
@@ -168,9 +168,9 @@ export const TABLES: { [M in ModelName]: TableDescriptor } = {
     primaryKey: "id",
     softDelete: "deletedAt",
     columns: [
-      { name: "id"; type: 'string'; required: true; list: false; unique: true; isEnum: false },
-      { name: "email"; type: 'string'; required: true; list: false; unique: false; isEnum: false },
-      { name: "deletedAt"; type: 'date'; required: false; list: false; unique: false; isEnum: false },
+      { name: "id", type: 'string', required: true, list: false, unique: true, isEnum: false },
+      { name: "email", type: 'string', required: true, list: false, unique: false, isEnum: false },
+      { name: "deletedAt", type: 'date', required: false, list: false, unique: false, isEnum: false },
     ],
     includedInSync: true,
   },
@@ -249,9 +249,17 @@ export const UserSchema = Schema.standardSchemaV1(Schema.Struct({
   email: Schema.String,
 }))
 
-// Works with Standard Schema consumers:
-UserSchema["~standard"].validate({ id: "u1", email: "a@b.c" })
-// => { value: { id: "u1", email: "a@b.c" } }
+// The wrapped schema still works as an Effect Schema...
+Schema.decodeUnknownSync(UserSchema)({ id: "u1", email: "a@b.c" })
+
+// ...and is accepted directly by Standard Schema consumers without
+// casting Context to `never`:
+import { createCollection } from "@tanstack/db"
+
+const users = createCollection({
+  id: "users",
+  schema: UserSchema, // Context is `never`, no `as never` needed
+})
 ```
 
 ## Programmatic use
@@ -300,6 +308,32 @@ npm test           # vitest
 npm run typecheck  # tsc --noEmit
 ```
 
+## Related projects
+
+### How is this different from `effect-prisma-generator`?
+
+This project is focused on **generating Effect Schema values** from your
+Prisma schema—standalone, serializable validators you can use anywhere
+(read-path validation, sync engines, RPC payloads, form validation, etc.).
+
+[`m9tdev/effect-prisma-generator`](https://github.com/m9tdev/effect-prisma-generator)
+takes the opposite approach: it generates an **Effect-native service wrapper
+around Prisma Client**, so every Prisma operation returns an `Effect` and
+plugs into Effect's `Layer` / `Context` system. It is great if you want to
+run Prisma through Effect's runtime.
+
+| | `prisma-effect-schema-generator` | `effect-prisma-generator` |
+|---|---|---|
+| Output | `Schema.Struct` values + introspection maps | `PrismaService` Effect service |
+| Needs Prisma Client at runtime | No | Yes |
+| Primary use case | Validate rows / introspect schema | Execute Prisma operations in Effect |
+| Relations | Optional `relationColumns` schemas | Full Prisma Client relation API |
+| Errors | Standard `Schema` decode errors | Typed `PrismaError` unions |
+
+If you need Effect-powered Prisma Client operations, use
+`effect-prisma-generator`. If you need portable Effect schemas and metadata
+from your schema, use this package.
+
 ## License
 
 MIT

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "prisma-effect-schema-generator",
-  "version": "0.1.3",
-  "description": "Prisma generator that emits Effect Schema values for every model — drop-in validation for your database rows.",
+  "version": "0.1.4",
+  "description": "Prisma generator that emits Effect Schema values, relation schemas, and runtime introspection maps (primary keys, soft-delete columns, table descriptors) for every model — drop-in validation for your database rows.",
   "keywords": [
     "prisma",
     "prisma-generator",