feat(QuickStarts): decouple content from quickstart drawer #344
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.
Closes #135.
QuickStartDrawerContent
component that may be used with a custom drawer. This acts as a replacement for a typicalDrawerContent
in aDrawer
.QuickStartDrawerContent
is also used internally for the current managed drawer implementation.QuickStartsCloseModal
to be used with custom drawers (though this could be done manually with a custom modal too, LMK if we want to let this be exported or not).isManagedDrawer
prop toQuickStartContainer
, defaulting totrue
QuickStartContainer
andQuickStartDrawer
into their own component files (both were exported in a single file)To use a custom drawer, you would use the same initial
QuickStartContainer
and context setup, and now passisManagedDrawer={false}
. Then within the container, use a directly managedDrawer
with the newQuickStartDrawerContent
as a child. Optionally, you may include aQuickStartCloseModal
that triggers onQuickStartDrawerContent
'shandleDrawerClose
callback to handle in-progress close confirmation.