create-fate 1.9.0 → 1.10.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-fate",
-  "version": "1.9.0",
+  "version": "1.10.1",
   "description": "Create a new fate app.",
   "homepage": "https://github.com/nkzw-tech/fate",
   "license": "MIT",

package/templates/fate/drizzle/client/src/ui/PostCard.tsx

@@ -78,7 +78,11 @@ const CommentInput = ({
   post,
 }: {
   error?: unknown;
-  post: { commentCount: number; id: string };
+  post: {
+    commentCount: number;
+    comments: Deferred<{ items: ReadonlyArray<{ node: ViewRef<'Comment'> }> }>;
+    id: string;
+  };
 }) => {
   const fate = useFateClient();
   const { data: session } = AuthClient.useSession();
@@ -94,6 +98,7 @@ const CommentInput = ({
 
     const result = await fate.mutations.comment.add({
       input: { content, postId: post.id },
+      insert: { into: post.comments, position: 'after' },
       optimistic: {
         author: user
           ? {

package/templates/fate/graphql/README.md

@@ -18,15 +18,14 @@ Read the [Getting Started Guide](https://fate.technology/guide/core-concepts) to
 
 ## GraphQL Types
 
-`client/src/fate/graphql.ts` imports the SDL exported from the Pothos schema during `dev:setup` and maps application root
-and mutation names. Fate generates `client/.fate/schema.generated.ts` from that
-schema; its `GraphQLEntities` types are used by the client views. Mutation inputs,
-output nullability, and connection shapes also come from the schema.
+After changing your GraphQL schema, regenerate the schema file and client types:
 
-Run `vp run --filter '@app/server' generate-graphql` after changing schema fields,
-then `vp run fate:generate` to update the client contracts. The server's
-Prisma data views implement live-event resolution and authorization; they are
-independent of these generated client contracts.
+```bash
+vp run --filter '@app/server' generate-graphql
+vp run fate:generate
+```
+
+`client/src/fate/graphql.ts` maps query and mutation names. Client views use `GraphQLEntities` from `client/.fate/schema.generated.ts`, generated from your Pothos schema. Server data views handle live updates and authorization.
 
 ## Technologies
 
@@ -126,7 +125,7 @@ Common commands from the project root:
 - `vp run dev:client` starts only the client.
 - `vp run dev:server` starts only the server.
 - `vp run dev:setup` generates the Prisma client, Pothos schema import map, fbtee setup, and fate client support.
-- `vp run fate:generate` refreshes fate client support after changing server views, roots, or routers.
+- `vp run fate:generate` regenerates client types after changing the GraphQL schema or client mapping.
 - `vp run prisma` runs Prisma CLI commands in the server package.
 - `vp check --fix` formats, lints, and type-checks the workspace.
 - `vp test` runs the test suite.

package/templates/fate/graphql/client/src/ui/PostCard.tsx

@@ -74,7 +74,11 @@ const CommentInput = ({
   post,
 }: {
   error?: unknown;
-  post: { commentCount: number; id: string };
+  post: {
+    commentCount: number;
+    comments: Deferred<{ items: ReadonlyArray<{ node: ViewRef<'Comment'> }> }>;
+    id: string;
+  };
 }) => {
   const fate = useFateClient();
   const { data: session } = AuthClient.useSession();
@@ -90,6 +94,7 @@ const CommentInput = ({
 
     const result = await fate.mutations.comment.add({
       input: { content, postId: post.id },
+      insert: { into: post.comments, position: 'after' },
       optimistic: {
         author: user
           ? {

package/templates/fate/graphql/server/README.md

@@ -14,7 +14,7 @@ vp run dev
 
 The server defaults to `http://localhost:9000/graphql`.
 
-The client mapping imports the SDL exported from the Pothos schema during `dev:setup`. From the client directory, configure the Vite plugin with:
+`vp run dev:setup` exports the GraphQL schema for the client. From the client directory, point the Vite plugin at the mapping module:
 
 ```ts
 fate({
@@ -23,6 +23,4 @@ fate({
 });
 ```
 
-Fate derives entity fields, connection roots, mutation inputs, and selected results from the schema.
-The server data views in `src/graphql/views.ts` remain responsible for live-event resolution,
-including authorization and computed fields. They do not define the GraphQL client types.
+fate generates client types from the schema. Server data views in `src/graphql/views.ts` handle live updates, authorization, and computed fields.

package/templates/fate/graphql-client/README.md

@@ -34,24 +34,16 @@ VITE_GRAPHQL_URL="https://api.example.com/graphql" vp run build
 
 These `VITE_*` values are embedded in the client bundle. Do not put credentials in them. Production builds do not read `.env`.
 
-Replace `src/fate/schema.graphql` with the schema exported by your existing
-GraphQL server, then edit `src/fate/graphql.ts` to map application names:
+Replace `src/fate/schema.graphql` with your server's schema, then edit `src/fate/graphql.ts`:
 
-- `fateGraphQL.schema` supplies the SDL used during generation.
-- `fateGraphQL.roots` exposes query fields and optionally maps different names
-  through `field`. Entity and connection types are inferred from the schema.
+- `fateGraphQL.schema` supplies the schema used to generate client types.
+- `fateGraphQL.roots` exposes query fields. Use `field` to map a different name.
 - `fateGraphQL.mutations` maps application mutation names to schema fields.
-- `fateGraphQL.scalars` optionally describes custom scalar wire types. Unmapped
-  custom scalars are `unknown`.
+- `fateGraphQL.scalars` optionally describes custom scalar types, which default to `unknown`.
 
-The sample schema includes `viewer`, `posts(first:, after:)`, `postLike(input:)`,
-`node(id:)`, and `nodes(ids:)`, with Relay-style connections. Replace it with your
-server's actual contract, including nullability and arguments.
+The sample schema includes `viewer`, `posts(first:, after:)`, `postLike(input:)`, `node(id:)`, and `nodes(ids:)`, with Relay-style connections. Replace these with your server's fields and arguments.
 
-Run `vp run fate:generate` to generate `.fate/schema.generated.ts`. Client views
-use `GraphQLEntities` from that file; there are no handwritten entity or mutation
-input types to keep synchronized. The schema and generation imports are excluded
-from the browser client.
+After changing the schema or mapping, run `vp run fate:generate`. Client views use `GraphQLEntities` from the generated `.fate/schema.generated.ts`. The schema stays out of the browser bundle.
 
 ## Development
 

package/templates/fate/http/client/src/ui/PostCard.tsx

@@ -74,7 +74,11 @@ const CommentInput = ({
   post,
 }: {
   error?: unknown;
-  post: { commentCount: number; id: string };
+  post: {
+    commentCount: number;
+    comments: Deferred<{ items: ReadonlyArray<{ node: ViewRef<'Comment'> }> }>;
+    id: string;
+  };
 }) => {
   const fate = useFateClient();
   const { data: session } = AuthClient.useSession();
@@ -90,6 +94,7 @@ const CommentInput = ({
 
     const result = await fate.mutations.comment.add({
       input: { content, postId: post.id },
+      insert: { into: post.comments, position: 'after' },
       optimistic: {
         author: user
           ? {

package/templates/fate/prisma/client/src/ui/PostCard.tsx

@@ -74,7 +74,11 @@ const CommentInput = ({
   post,
 }: {
   error?: unknown;
-  post: { commentCount: number; id: string };
+  post: {
+    commentCount: number;
+    comments: Deferred<{ items: ReadonlyArray<{ node: ViewRef<'Comment'> }> }>;
+    id: string;
+  };
 }) => {
   const fate = useFateClient();
   const { data: session } = AuthClient.useSession();
@@ -90,6 +94,7 @@ const CommentInput = ({
 
     const result = await fate.mutations.comment.add({
       input: { content, postId: post.id },
+      insert: { into: post.comments, position: 'after' },
       optimistic: {
         author: user
           ? {

package/templates/fate/void/db/migrations/20261015035853_better_auth_accounts.sql

@@ -1,3 +1,4 @@
+-- void:allow-destructive
 DROP INDEX `account_issuer_accountId_key`;
 --> statement-breakpoint
 ALTER TABLE `account` DROP COLUMN `issuer`;

package/templates/fate/void/src/ui/PostCard.tsx

@@ -92,7 +92,11 @@ const CommentInput = ({
   post,
 }: {
   error?: unknown;
-  post: { commentCount: number; id: string };
+  post: {
+    commentCount: number;
+    comments: Deferred<{ items: ReadonlyArray<{ node: ViewRef<'Comment'> }> }>;
+    id: string;
+  };
 }) => {
   const fate = useFateClient();
   const { auth } = useShared<SharedData>();
@@ -108,6 +112,7 @@ const CommentInput = ({
 
     const result = await fate.mutations.comment.add({
       input: { content, postId: post.id },
+      insert: { into: post.comments, position: 'after' },
       optimistic: {
         author: user ? { id: user.id, name: user.name } : null,
         content,