fix: do not provide default colors for ConfigProvider #538
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.
SUMMARY:
ConfigProvider is currently providing default values unnecessarily. This makes it necessary to provide empty objects in config in order to avoid the undesired default values.
![Screenshot 2023-02-08 at 2 43 11 PM](https://user-images.githubusercontent.com/106610186/217646757-9a9ff57f-2c71-491f-8cf1-f36dff0a4c0a.png)
In this example, I'm trying to emulate a starbucks green theme, and if I don't provide an empty navbarTheme and tabsTheme then the defaults get copied in and I end up with blue tabs despite my varTheme.
CHANGE TYPE:
TEST COVERAGE:
TEST PLAN:
Pull down the PR and run storybook locally. Select a new primary and/or accent color in ConfigProvider story. With this change, the tabs get updated appropriately. Current undesirable behavior is that they stay blue based on the default values.