create-rindle 0.7.12 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-rindle",
3
- "version": "0.7.12",
3
+ "version": "0.8.0",
4
4
  "license": "Apache-2.0",
5
5
  "repository": {
6
6
  "type": "git",
@@ -29,9 +29,9 @@ Three tiers, same as the Rindle flagship examples:
29
29
 
30
30
  The schema lives in `migrations/*.sql`. The `@rindle/client` table schema is **generated** from it
31
31
  into `shared/schema.gen.ts` (re-exported by `shared/app-def.ts`, which layers on the relationships,
32
- normalization, and mutators) — so the TypeScript can't drift from the DDL. To change the schema, edit
33
- or add a `migrations/*.sql`; `pnpm dev` re-applies it and regenerates `shared/schema.gen.ts` on every
34
- change.
32
+ normalization, and mutators) — so the TypeScript can't drift from the DDL. To change the schema,
33
+ add a new ordered `migrations/*.sql`; `pnpm dev` applies it and regenerates `shared/schema.gen.ts`
34
+ on every change.
35
35
 
36
36
  ## Run it
37
37
 
@@ -5,8 +5,9 @@
5
5
  -- @rindle/client TypeScript schema is GENERATED from the daemon's introspected result into
6
6
  -- shared/schema.gen.ts — so the TS can't drift from the DDL.
7
7
  --
8
- -- To change the schema: add or edit a file in migrations/. `pnpm dev --watch` re-applies it and
9
- -- regenerates shared/schema.gen.ts automatically; `pnpm migrate` does the same for a one-shot run.
8
+ -- To change the schema after this file has been applied, add a NEW ordered file in migrations/.
9
+ -- `pnpm dev` applies it and regenerates shared/schema.gen.ts automatically; `pnpm migrate` does the
10
+ -- same for a one-shot run.
10
11
  --
11
12
  -- Column kinds map to the client schema like so: TEXT → string(), INTEGER/REAL → number(), a column
12
13
  -- declared BOOLEAN/BOOL → boolean(), JSON → json(). Column ORDER matters — the IVM engine reads it