You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version of browser: Chrome Version 97.0.4692.71 (Offizieller Build) (64-Bit)
Version of geist-ui/core: 2.2.3
Expected Behaviour
The behavior I expect is that a custom theme created through the customization interface changes the way components (e.g.: Button) look like.
I am testing this in a default CRA with TypeScript app.
Actual results (or Errors)
The Button component uses the default "lite" theme.
I checked via the "Component" explorer of the React devtools. There is a "GeistProvider" with my custom theme and themeType: "Custom". Further down the tree there is a "ThemeProvider" with the same values, followed by two "ContextProvider". The first of which holds all the themes (light, dark and custom) while the second one only holds the custom theme. Moving further down I find "ScalableGeistButton" which uses a Theme hook that returns the light theme as the Context. Super confused how that happens.
Bug report 🐞
Version & Environment
geist-ui/core
: 2.2.3Expected Behaviour
The behavior I expect is that a custom theme created through the customization interface changes the way components (e.g.: Button) look like.
I am testing this in a default CRA with TypeScript app.
Actual results (or Errors)
The Button component uses the default "lite" theme.
I checked via the "Component" explorer of the React devtools. There is a "GeistProvider" with my custom theme and
themeType: "Custom"
. Further down the tree there is a "ThemeProvider" with the same values, followed by two "ContextProvider". The first of which holds all the themes (light, dark and custom) while the second one only holds the custom theme. Moving further down I find "ScalableGeistButton" which uses a Theme hook that returns the light theme as the Context. Super confused how that happens.The text was updated successfully, but these errors were encountered: