Generated by XState Viz: https://xstate.js.org/viz

100%

Generated by XState Viz: https://xstate.js.org/viz

✓ Published0🌍 Public

Last edited Mar 16, 2021

Created on Mar 16, 2021

This example shows a login state machine built with XState, modeled as an explicit statechart with idle, loading, success, and failure states. It demonstrates asynchronous data fetching by invoking a `fetchJwt` function that retrieves a JSON Web Token from a remote URL. The machine uses the `invoke` property with `onDone` and `onError` transitions, assigning the returned user data or an error to the context via the `assign` action. The visualization, generated by XState Viz, renders the statechart diagram from the `machine.js` source file, highlighting how state transitions and async side effects are encoded in the machine definition.

AI-generated description

Similar vizzes

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

XState Viz renders a statechart for an asynchronous data-fetching machine, showing transitions between idle, pending, failed, and successful states. The successful state contains nested substates (unknown, withData, withoutData) using conditional guards. The code defines the machine with XState's `Machine` API, including `invoke` for a `fetchData` promise, `assign` actions for setting results or error messages, and a guard `hasData` that always returns false. The visualization displays the full state graph with labeled transitions and event-driven flows.

Aafbroman

82% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This example shows a finite-state machine for fetching data, with four states—idle, loading, success, and failure—and transitions triggered by FETCH, RESOLVE, REJECT, and RETRY events. The machine uses XState’s `Machine`, `assign`, and `interpret` APIs, with a `context` object tracking retry attempts. It demonstrates how statecharts handle asynchronous flows, incrementing a retry counter on each failed attempt before returning to loading. The visualization is generated by XState Viz, which renders the machine’s structure and event-driven transitions from the provided machine definition.

HHerbCaudill

81% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This example shows a parallel state machine for user management, with three concurrent sub-machines tracking login status, user data loading, and client data loading. XState Viz renders the machine definition into an interactive diagram, displaying each sub-machine’s states and transitions. The code uses the `Machine` and `interpret` APIs from XState to define a `userManagement` machine with parallel states, where events like `LOGIN_SUCCESS` and `LOGOUT` trigger coordinated transitions across all three regions. The visualization updates live to reflect the current state configuration.

Aadamscott

77% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This example shows a state machine for an SSL quote creation workflow, modeled with XState and visualized by XState Viz. It maps user interactions—like clicking a create button, searching or selecting accounts, and progressing through opportunity and contract stages—to nested and parallel states. The machine defines actions such as fetching account lists and opportunities, while transitions manage UI elements like buttons, tables, and accordions. The source code is written in plain JavaScript, using the `Machine` constructor from XState, and the visualization is generated automatically by the XState Viz tool.

Aajayullal

76% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This visualization shows a state machine for a multi-step signup and onboarding flow, navigating through states like signup, sniffer, validate, industry, objective, and browse. It uses XState’s `Machine` API to define hierarchical states, transitions, guards (e.g., `hasNotSniffed`, `isNotValidated`), and actions like `goNext` and `goBack` that update the context’s direction. The rendered diagram, generated by XState Viz, illustrates conditional branching on events like `NEXT` and `BACK`, with exit actions assigning `hasSniffed: true` after leaving the sniffer state.

Aadamscott

75% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This visualization shows a finite-state machine for a workstation’s connection and request lifecycle, modeled with XState’s `Machine` API. It begins in a `start` state, transitions through `connection` and `request`, and terminates in a `response` state where various success, cancellation, or error events lead to final states. The code assigns context values like `responseStatus`, `pedId`, and `approvalCode` using `assign` actions, and defines transitions for events such as `CONNECTING`, `PENDING`, `SUCCESS`, and `TIMED_OUT`. The machine is rendered by XState Viz, which visualizes states and transitions from the provided machine definition.

TTimeBandit

75% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This visualization shows a state machine for creating an SSL quote, modeled with XState’s `Machine` API. It maps user interactions—such as clicking a create-quote button or searching an account—to transitions between states like Home, Opportunities, and Contract, including nested sub-states for account listing and selection. The code uses `entry` actions to fetch accounts and opportunities, and defines explicit events like `Select Account` to enable or disable UI buttons. The rendered diagram, generated by XState Viz, displays the state hierarchy and transition paths directly from the machine definition.

Aajayullal

72% match

Loading thumbnail…

Generated by XState Viz: https://xstate.js.org/viz

This example shows a state machine for a free-trial signup flow, progressing from an idle state through name entry to an email state. The machine starts in `idle`, waits for a `READY` event, then moves to `name`, where an entry action logs the context and event before automatically raising a `NEXT` event to transition to `email`. It uses XState’s `Machine` and `raise` API to define states, transitions, and context with a `retries` counter. The code includes a custom `nameEntry` action that triggers the next step programmatically.

Aadamscott

69% match