Marco Massarotto
Marco Massarotto
@xiaoye97 did you have a chance to look at this PR ?
@jdalton : can you please provide an update ? this is a deal breaker for me (and i guess for many others)
@quantizor doesn't look like this should be a breaking change as it's actually an undocumented regression
> I think this is potentially a breaking change, probably can't land it safely in the current major version Any chance you can get this merged ?
> I decided to patch it myself locally with `patch-package` npm package We are doing the same with yarn patch. The fact that this has not yet been merged is...
The examples focus on the js apis and they do not extend DefaultTheme interface or care about types as its not the purpose of the example. Typescript support is documented...
> Thanks @brokenmass for your quick reply... > > what i'm saying is 1) it's a bit hard for "bug fix release" to put that in... and 2) i'm not...
if you are sure the inner ThemeProvider is always rendered inside another one then you can use a non-null type assertions `!.` where needed: ```ts ({ ...theme, colors: { ...theme!.colors,...