Skip to content

walkerOS v4.8.1

Latest

Choose a tag to compare

@github-actions github-actions released this 15 Oct 05:59

Changes

elb takes an event object,
elb({ name, data, trigger, context, nested, custom }), a command,
elb('walker <command>', data), or the string form
elb('entity action', data). The positional context, nested and custom
arguments are gone, and a second argument after an event object is no longer
merged into data. Such arguments are ignored and reported as an error. The
string form takes data only when it is a plain object; before, any non-array
object, such as an element or a date, was taken.

Adds the on-event design token: text on an event-colour fill, such as a tag
card's Done button. Dark ink on the dark event colours, white on the light ones,
both above 4.5:1.
Adds EventLog to the design components: the walkerOS events of a session,
newest first, beside the selected event as fields or as JSON, with copy and
clear.

frame_manage returns the frames a frame shows as links and its variant group
as variantSetId. parentId, extends and placements are gone from its
output, from the exported frame types and from what the CLI's listFrames,
listPageFrames and getFrame return. A page read returns that page's frames
only. FRAME_HINT_EXTENDS_BASE is now FRAME_HINT_FOLLOW_LINKS. Needs the
walkerOS app release that serves links.

The walkeros://reference/examples resource now ships inside the package, so it
also works when a host bundles the MCP server. Before, a bundled server answered
Example not found instead of the complete flow example, because it looked the
file up on disk at runtime.

New walkeros api sends any request to the walkerOS app API, walkeros api ls
lists its operations, walkeros auth token prints your token. The typed remote
commands (projects, flows, deploy, previews, observe, feedback) and their
programmatic functions are gone. The local MCP server keeps the flow tools;
saved flows and deployments move to the hosted server at
app.walkeros.io/api/mcp.

walker.js and every web bundle the CLI builds now carry the Tag Mode loader,
moin() from @walkeros/core. It stays idle unless the walkerOS app opens your
page for Tag Mode (?elbMoin), then loads the Tag Mode script from
cdn.walkeros.io. Without that host in your CSP's script-src, it loads
nothing (a 'strict-dynamic' policy admits it through walker.js's nonce).

elb takes an event object,
elb({ name, data, trigger, context, nested, custom }), or a walker command.
The string form elb('entity action', data) still works and sends exactly
{ name, data }. Any argument after data or after the event object, and
data that is not an object (such as an element), is ignored and reported as an
error: put trigger, context, nested and custom inside the event object. The
types BrowserArguments, BrowserPushData, BrowserPushOptions and
BrowserPushContext are removed.
The automatic page view uses the path as data.id unless the page tags an id; a
page event you push keeps its data as written. elb no longer writes source
or globals onto the event or data object you pass in.
An event that carries its own globals keeps the globals tagged on the page as
well; the event's values win per key.

Published Packages