diff --git a/.changeset/config.json b/.changeset/config.json index eeab345fdc..d9f44e5375 100644 --- a/.changeset/config.json +++ b/.changeset/config.json @@ -14,6 +14,9 @@ "updateInternalDependencies": "patch", "ignore": [ "scratchpad", + "@forgerock/devtools-extension", + "@forgerock/devtools-bridge", + "@forgerock/devtools-types", "@forgerock/pingone-scripts", "@forgerock/device-client-app", "@forgerock/davinci-app", diff --git a/.changeset/quiet-onions-study.md b/.changeset/quiet-onions-study.md new file mode 100644 index 0000000000..7c5df1f6e7 --- /dev/null +++ b/.changeset/quiet-onions-study.md @@ -0,0 +1,6 @@ +--- +'@forgerock/journey-client': minor +'@forgerock/oidc-client': minor +--- + +Adds subscribe method to public api diff --git a/.changeset/seven-hoops-win.md b/.changeset/seven-hoops-win.md new file mode 100644 index 0000000000..26c65248e1 --- /dev/null +++ b/.changeset/seven-hoops-win.md @@ -0,0 +1,5 @@ +--- +'@forgerock/davinci-client': minor +--- + +Adds a get cache method to expose the cache for consumers like devtools diff --git a/.gitignore b/.gitignore index 327a931c1a..922c4ca6c1 100644 --- a/.gitignore +++ b/.gitignore @@ -5,6 +5,9 @@ .pnpm-store/* .npm/_logs +# Elm +elm-stuff/ + # Generated code logs/* tmp/ diff --git a/.prototools b/.prototools new file mode 100644 index 0000000000..adf7bdaa9d --- /dev/null +++ b/.prototools @@ -0,0 +1,5 @@ +node = "22" +pnpm = "10" + +[settings] +auto-install=true diff --git a/.superpowers/brainstorm/694753-1778353306/content/learn-error-states.html b/.superpowers/brainstorm/694753-1778353306/content/learn-error-states.html new file mode 100644 index 0000000000..15435e557b --- /dev/null +++ b/.superpowers/brainstorm/694753-1778353306/content/learn-error-states.html @@ -0,0 +1,530 @@ +
+ When a step fails, how should the lifecycle show it? Here's a scenario: Server returns 401 + Unauthorized. +
+ ++ The arrow between server and SDK shows a visible ✕ break. The SDK card turns red with a + pulsing ring. Downstream stages (collectors/form) are ghosted out with dashed borders and + "skipped" label. Error banner below explains what happened. The flow visually stops at the + failure point. +
++ The card where the error originated (SERVER) gets a red border, pulsing glow, and a "401" + badge. All downstream cards also turn red to show error propagation, but only the source + card pulses. Downstream form is ghosted. Error detail card below shows specifics anchored to + the source. +
++ Hybrid layout confirmed. Now let's nail the icons and visual language for the step lifecycle. + Which icon style feels right? +
+ ++ Clean outlined icons — browser with traffic-light dots, rack server with status LEDs, gear + for SDK processing, form fields for collectors. Arrows show direction and label the action. + Loopback arrow shows the cycle repeating. Status pills below summarize each stage. +
++ Each stage is a card with a recognizable icon inside — browser window with globe, cloud + server with status dots, gear for SDK processing, form with input fields. Arrows are labeled + inline. Bolder, more visual weight. Cycle arrow wraps around to show the loop. +
++ How should the flow diagram be oriented? Consider that auth flows can have 3-15+ steps. +
+ ++ Natural reading direction. Flow overview scrolls horizontally. Detail panel below selected + node. Works well with pan/zoom for long flows. +
++ Like the existing Graph panel but expanded. Flow scrolls vertically. Detail panel to the + right of selected node. Familiar pattern from current UI. +
++ Horizontal rail at the top (like existing FlowView) for the full flow overview. Below, an + expanded step-detail section shows the internal lifecycle: Request → Server → Response → + Node → Collectors. Click a node in the rail to drill in. Keeps context while showing detail. + The detail section is the draggable canvas. +
+Continuing in terminal...
+Continuing in terminal...
+