create-fate 1.11.1 → 1.12.0

package/package.json

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

package/templates/fate/graphql/AGENTS.md

@@ -23,7 +23,7 @@ This guidance is for agents working in projects bootstrapped from the fate templ
 - **Use ViewRefs:** Pass references instead of raw data. Keep components focused on views and `ViewRef`s to let fate manage data masking and updates.
 - **Co-locate data needs:** Keep view definitions near their components and compose them upward to the request root for predictable fetching.
 - **Use Suspense:** Wrap pages in `Suspense`/`ErrorBoundary` instead of ad-hoc loading/error flags; fate aligns with Async React by design.
-- **Do not duplicate types:** Use `GraphQLEntities` from `client/.fate/schema.generated.ts` for GraphQL view types. The client mapping exports convenient aliases; avoid redefining entity shapes on the client. This ensures view selections stay type-safe end-to-end.
+- **Do not duplicate types:** Use `GraphQLEntities` from `client/.fate/client.generated.ts` for GraphQL view types. The client mapping exports convenient aliases; avoid redefining entity shapes on the client. This ensures view selections stay type-safe end-to-end.
 - **`useRequest` only at the root:** When adding routes or layouts, create a dedicated `useRequest` call per screen root that pulls together all child views; do not scatter `useRequest` across leaf components unless it's necessary to issue requests due to user input.
 - **React Actions:** Prefer React Action-friendly UI primitives (buttons/forms that accept an `action` prop). If unavailable, wrap action calls with `startTransition` in `onClick` handlers.
 - **fate client support** fate's local client support files are maintained by the Vite/fate tooling. Do not manually edit `.fate` files; make the proper schema changes on the server and run `pnpm fate:generate` when working outside Vite dev.

package/templates/fate/graphql/README.md

@@ -25,7 +25,7 @@ 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.
+`client/src/fate/graphql.ts` maps query and mutation names. Client views use `GraphQLEntities` from `client/.fate/client.generated.ts`, generated from your Pothos schema. Server data views handle live updates and authorization.
 
 ## Technologies
 

package/templates/fate/graphql/client/src/fate/graphql.ts

@@ -1,5 +1,5 @@
 import schema from '@app/server/src/graphql/schema.graphql?raw';
-import type { GraphQLEntities } from '../../.fate/schema.generated.ts';
+import type { GraphQLEntities } from '../../.fate/client.generated.ts';
 
 export type User = GraphQLEntities['User'];
 export type Post = GraphQLEntities['Post'];

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

@@ -43,7 +43,7 @@ Replace `src/fate/schema.graphql` with your server's schema, then edit `src/fate
 
 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.
 
-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.
+After changing the schema or mapping, run `vp run fate:generate`. Client views use `GraphQLEntities` from the generated `.fate/client.generated.ts`. Schema types are erased from the browser bundle.
 
 ## Development
 

package/templates/fate/graphql-client/src/fate/graphql.ts

@@ -1,4 +1,4 @@
-import type { GraphQLEntities } from '../../.fate/schema.generated.ts';
+import type { GraphQLEntities } from '../../.fate/client.generated.ts';
 import schema from './schema.graphql?raw';
 
 export type User = GraphQLEntities['User'];