Skip to content

Flows: Add fuctionality or remove Finish button #2893

@navillanueva

Description

@navillanueva

At the end of my guides, the finish button is useless - doesn't display success message, doesn't lead to any page.

As a preparation for this task we are doing #2929 which create a single source of truth for console tool titles and requirements. it also add a onSuccess() callback for the tools. This can then be used by the flows for guiding the user to the next step.

The flow can render on the onSuccess call a dismissable overlay "What's next?". If there is only a single option the user can just switch over. If there are multiple options (for example L1 Node Setup with Docker or Managed Testnet Nodes), the flow can show both options and the user selects.

To-Do's:

  • Change flows to use title and if it's a testnet only tool from metadata instead of manually configured title
  • use the onSuccess handler of the tool to jump to the next tool in the flow
  • for steps with multiple alternatives (e.g. L1 Node Setup: Docker vs managed testnet node) have an intermediate screen outlining both options and guiding the user which one to use under what circumstances

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Ready

Relationships

None yet

Development

No branches or pull requests

Issue actions