`fix(ui): Storybook's <DocsContainer /> overwriting theme object #29770
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.
Storybook's
<DocsContainer />
implements its own theme context. In the current configuration, that theme context is a descendant of the custom theme context that we implemented:This means

DocsContainer
's theme object will overwrite any property in our theme object. This is a problem because both have thebackground
property. Any component insideDocsContainer
will see onlyDocsContainer
'sbackground
and not ours:To fix this, we can move our custom

ThemeProvider
context insideDocsContainer
, making it more specific and thus overwriting whatever value is inDocsContainer
's theme. As a result, components insideDocsContainer
will now get the correct theme values: