Repository navigation
v0.16.18
- 0.16.18 (62fa4f4)
- Waygraph UI: a page on the map lists what it shows, the fields its Read Blocks read by namespace, the yes/no ones highlighted as the states the page can be in. Each box is as tall as its list (measured once drawn), and the layout sizes each column and row to its boxes and moves a subtree down when its page is taller than its children, so no box covers another. UI guide (f1fd1f7)
- Accounts say who their person is: account(name, { signIn, mem }) sets the person's data (an email for a magic link) right before signing in, so a flow as the account needs nothing more and an earlier flow's person doesn't carry over; its keys aren't asked of flows as it. Waygraph loads src/accounts/ (runs, demos, waygraph test), so a sign-in flow that is one account's, played on its own (waygraph demo loginLeadershipFlow, or Run in Waygraph UI), signs in as that person without --data (a --data value still wins). MemPage.keys(). Tests, flows guide, convention skill, planner agent (0d7d8d9)
- Waygraph UI: the sidebar's pages can be hidden (Settings, kept in the browser; a hidden page still opens by its address and shows while you're on it). The map makes room for its labels: lines into a page put their Blocks beside it (before it from an earlier column, after it from its own), stacked when several meet there, and the layout widens each gap and row to fit them, so a label never covers a box or another label. Icons named in .ts files are bundled too. UI guide (378a2d0)
- Page objects and waygraph: a docs page (what waygraph adds to a page object model, part for part; measured side by side; adopting it one flow at a time with Blocks that call existing page objects) and examples/pom-vs-waygraph, the same Sauce Demo checkout as page objects, as waygraph, and as Blocks wrapping the page objects, played against UI changes (npm run compare). A failure inside a step's act names its step (act of "sign-in" failed: ...) and stays the error it was; the run log's step:error keeps the error's own text. Tests, checks guide, README (2eecd92)
- A Checkpoint is a page, in the examples and the scaffold. saucedemo and the quickstart drop ItemInCart: adding or removing an item (one, or all) leaves you on the inventory, and its verify checks what the inventory shows (each item's inCart) instead of resolving to another Checkpoint. The scaffold drops ItemInCart, CartEmpty, CanAddItem and HomeVerified: add, remove and clear stay on Home and check home.items / home.cartCount; the verification link lands on Home with home.verified; the item-added expectation is HomeRead.cartCount.is(1) in place. Guides (blocks, flows, reads, mail, how it works, home), convention skill, tests (3ec9aa5)
- Reads guide: nothing imports a Read Block; run, demo, test and the live sessions load them (7fdec95)
- waygraph test loads the project's Read Blocks, as run and demo do: a verify or expect that checks what a page shows (Key.is / passes) read nothing in a spec or a flow test unless its flow imported the Read Block file. Test (a flow test whose verify reads through a Read Block no flow imports) (7d1414e)
- waygraph check names a Checkpoint that is a state of a page: nothing starts from it, and it has no address of its own and only Methods land on it (an item in the cart, a link sent), or only another page's address (an alert on the sign-in page). What changed on a page is a Read Block's field, checked in verify or expected. Doctrine (a Checkpoint is a page), blocks guide, convention skill, tests (a5ac44b)
- Waygraph UI: a Project page. The project's waygraph commands as buttons (check, validate, typecheck, map, graph, list, nav, manifest, test, test --flows, upgrade, extensions install, upgrade --skills and the codemods, which ask first), run with its own waygraph, one at a time, their output as they print; Stop ends one and what it started, and it says stopped. And the project's config: what it resolves to, or the file as written. waygraph manifest reports config: the config file and its resolved values as JSON (a function as a word). Tests, docs (UI guide, manifest), ROADMAP (224cef8)
- Waygraph UI: a Blocks page. Every Block by its folder (kind, route, what it requires and expects, its file, the flows that use it), found by name, page or file and filtered by kind; from the newest runs, how often it ran and failed, its mean time, and what it did to the address: navigates (its step ended on another path: a redirect, a single-page app's routing) or changes the address (same page, the query or hash changed: a tab, a filter). Read Blocks with their fields' types, and mem keys with who requires each and the newest run's value. Tests, UI guide (f438f53)
- Waygraph UI: the map has a page tree beside it, the site map as folders (sites, path folders, pages with their addresses): check or uncheck to show or hide a part, only to keep one branch (just the equipment pages), All / None, find by name or path; the choice is kept per project in the browser, and the map lays out and fits what's shown, beside the tree. waygraph's Start isn't a page on the map. UI guide (978f914)
Full changes: v0.16.17...v0.16.18