Examples
Files under examples/: what each is for and which surface uses it.
| File | What it is | Used by |
|---|---|---|
examples/demo_schema.eel | Users schema (email indexed, Money<usd>, status enum) | eelgrass run, Studio HMR seed (npm run dev → mydb-studio), eelgrass serve / eelgrass studio with this schema, eelgrass-codegen via config |
examples/demo_queries.eel | Inserts alice/bob/carol + select/filter pipelines | eelgrass run; Studio npm run dev seeds the DB with this file |
examples/storefront.eel | Listings + Orders (ref), atomic checkout, join/sort/take, asof, fork tenant | Illustrative storefront scenario for eelgrass run / language reading. Studio HMR uses demo_schema.eel instead. |
examples/eelgrass.config.json | Codegen config: schema demo_schema.eel, queries queries/**/*.eel, outDir generated | eelgrass-codegen --config examples/eelgrass.config.json |
examples/queries/users.eel | Named queries ListUsers, GetPaid, ActiveUsers (use schema "../demo_schema.eel") | Named-query codegen (eelgrass-codegen) |
Quick runs
bash
# Seed + print demo pipelines
cargo run -p eelgrass-cli -- run ./mydb examples/demo_schema.eel examples/demo_queries.eel
# Named-query TypeScript bindings → examples/generated/
eelgrass-codegen --config examples/eelgrass.config.json
# Studio against the demo schema (after building the UI)
cargo run -p eelgrass-cli -- studio ./mydb-studio examples/demo_schema.eel --ui clients/studio/distStudio's npm run dev also seeds mydb-studio from demo_schema.eel + demo_queries.eel when the DB is missing. The in-tab Playground uses its own embedded Users / Listings / Orders catalog. It does not load these files. Example groups: Reads · Pipeline · Join · Time travel · Writes (storefront-shaped demos for join / group / asof that the serve-backed Users rail does not carry).