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) | eelden run, Studio HMR seed (npm run dev → mydb-studio), eelden serve / eelden studio with this schema, eelden-codegen via config |
examples/demo_queries.eel | Inserts alice/bob/carol + select/filter pipelines | eelden 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 eelden run / language reading — not the Studio HMR default schema |
examples/eelden.config.json | Codegen config: schema demo_schema.eel, queries queries/**/*.eel, outDir generated | eelden-codegen --config examples/eelden.config.json |
examples/queries/users.eel | Named queries ListUsers, GetPaid, ActiveUsers (use schema "../demo_schema.eel") | Named-query codegen (eelden-codegen) |
Quick runs
bash
# Seed + print demo pipelines
cargo run -p eelden-cli -- run ./mydb examples/demo_schema.eel examples/demo_queries.eel
# Named-query TypeScript bindings → examples/generated/
eelden-codegen --config examples/eelden.config.json
# Studio against the demo schema (after building the UI)
cargo run -p eelden-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 — not these files — with example groups Reads · Pipeline · Join · Time travel · Writes (storefront-shaped demos for join / group / asof that the serve-backed Users rail does not carry).