refactor(app): add and use deck map component in interventionmodal #15570
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds DeckMapContent to intervention modal. This is a small wrapper around one of two different kinds of deck map:
Stories for the deckmap are on storybook, where it's rendered side-by-side with the standin since it is only destined to be used in a two-column layout.
Extra fun changes:
BaseDeck
, because otherwise they are completely unreadable once the deckmap gets to small. I think this looks a lot better everywhere, and is actually readable when the deckmap is small, so let's go with it; may want to come back and make these something more specific on desktopRecoveryMap
, a large data structure that is core to the wizard flow and defines how users move between steps and screens. Error recovery also had aRecoveryMap
, which was a component for rendering a deckmap, and auseRecoveryMapUtils
, a hook for getting that component's arguments. Now it uses theDeckMapContent
component above directly, anduseDeckMapUtils
, a hook for getting that component's argumentsReview requests:
Testing, todo:
Closes EXEC-501