Repository navigation
v0.16.16
- 0.16.16. The UI guide says the map's addresses and page screenshots need 0.16.16 or later in the project (98037d9)
- Waygraph UI: the map reads like a site map, one level per part of the address. A path segment no page has is a folder (auth/, platform/, then plant/), so /platform/plant/lines sits three levels in instead of every page hanging off its site on one line; a folder's children follow the journey. The site map is worked out on the server (services/site_map.ts) and passed to the map page. Tests, UI guide (676973a)
- Effect Blocks are removed: an Effect was a Method that also listed the rows it can act on, and a Method lists them the same way (requires + instanceOptions; waygraph auto still offers one menu row each). defineEffectBlock, EffectBlock, EffectExtras and the effect kind are gone; waygraph upgrade --codemod effect makes them Methods, imports each name once, and renames *.effect.block.ts to *.method.block.ts with the imports that name them. The saucedemo example, the quickstart and the scaffold are converted by it (their graph is unchanged). Waygraph UI shows an old run's effect step as a Method. Docs (blocks, how it works, flows, project, saucedemo, pilot, agents, map, UI, README), skills and agents, the removed page (0.16.16), tests (bdfa2fb)
- Waygraph UI: a flow opens in Playwright UI on its own (Playwright UI next to Run and Demo: the Playwright page with only that flow's test, -g on its title; Show all flows goes back to every one; another flow restarts it over that one). Header spacing. UI guide (ad47395)
- Waygraph UI: a Playwright page runs Playwright's UI mode over the project's flows inside the app (waygraph test --flows on a free port, in a frame; Stop ends it and its browsers, so does the app's shutdown), and a Settings page (the gear) with Demo: Auto-advance, on by default: a demo started from the UI passes --auto-next or --no-auto-next. The waygraph launcher passes SIGTERM and SIGHUP on to the CLI (a kill left a UI server or a demo's browser running) and waits for it on Ctrl-C. Tests, UI guide, ROADMAP (96586af)
- Waygraph UI: a page's flows read plainly: how many land, may land and act there, then how their newest runs went (passed, failed, stopped, never run); listed in that order. A run with no flow named (a test calling flow.run) counts for the flow whose steps it played. waygraph test --flows names each flow in its run log. Tests, UI guide, run log reference (1e9944a)
- Waygraph UI: each page on the map says how many flows pass through it and how many failed their newest run; its panel lists them, each with how it gets there (lands, may land: a step with several outcomes that ends the flow, or acts there) and its newest run's outcome, linked. A flow's newest run settles where a step with several outcomes landed. A run of one flow plays again as a run or as a demo (Run again, Demo again), with the mem it was seeded with. Tests, UI guide (03191de)
- Demo: a step that loads a new page partway (a login landing on another document) keeps its collapsed panel with the steps' progress; the running panel is a piece of the overlay layer and is painted again on the new page. The rings after a step skip at once what its checks saw before the page changed, instead of waiting 30s for each (a login step stalled a minute). Test, demo guide (a5c6fce)
- Waygraph UI: a page's Shows lists what its Read Blocks read as a tree, grouped by namespace: each field with its type as a badge (text, number, yes/no in their own colours), a list's item fields nested under it, instead of the raw JSON shape (48e2f6c)
- Waygraph UI map: each Block on a line is a badge with its whole name, in its kind's colour (Nav blue, Method grey, Effect amber, API green), with a key in the bottom bar; no more names cut short or folded into +N. A line into the next column ends its badges at its arrowhead, over the boxes, on an opaque background; columns sit further apart to give them room. Kind colours live in one place (lib/kinds.ts) (f9fffd6)
- Screenshots, the map as a flowchart, and the demo's finish card. A Block's screenshot option (true, or { fullPage: true }) takes a picture as the last thing in its step; on a Page Block, whenever a step lands on its page. The run log keeps each with its run (runs//-.png, a run:artifact naming the step and the page) and each page's newest (screenshots/.png); the overlay is left out of the picture, and a screenshot never fails a step. The saucedemo example and the scaffold's pages take them. Waygraph UI shows a page's newest on the map and in its panel, and each step's on the run. The map reads left to right by default (a run of pages in a grid; a switch lays it out top down), in squared lines, each in its own lane, with moves within a depth bracketed past the boxes; flowchart shapes (terminator for a site or a step to a page, process, predefined process for a fast-forward, input/output for an API step); panels with a visible outline. The demo ends on a finish card over a veil: Finished, Finished as expected, or Stopped with where and why, the title and steps and time, held a moment so a recording ends on it. npm run ui / ui:dev run this checkout's Waygraph UI on saucedemo. Tests, stories, docs (blocks, demo, UI, run log), skill (d1f64f1)
- waygraph ui serves on 9294 by default ("WAYG" on a phone keypad), not 3333, which AdonisJS and other dev servers use; still the next free port when it's taken. The UI's dev .env, CI, help and docs follow (e2fed26)
- Waygraph UI: the map is a site map, and every page and step shows its address. Each site sits at the top (the base url's host, and every other site a page's address names), its pages below by their paths, dashed and labelled with the Navs that open them; a page with no address hangs under the page whose move reaches it; rows follow the order the flows visit pages. Pages, flow steps and run steps show their url (a run step: where it ended; the panel links it). The manifest gains each Nav or Page Block's url (a url built from mem as a pattern, /requests/:id), pageUrls (by Checkpoint, from Navs and the Trait.url its Blocks verify) and the project's baseUrl; a run's step:end carries the page's url. A CHROME_PATH that doesn't exist is ignored without a word. Tests, docs (UI guide, run log and manifest, config) (377ef8f)
- Docs: Waygraph UI is marked beta (guide, sidebar, README), says it comes with waygraph 0.16.13+ on Node 24 and runs the project's own waygraph, and shows up where a new user looks: the quick start and the home page (npx waygraph ui) and waygraph init's command list (591bf02)
Full changes: v0.16.15...v0.16.16