LoiKos

Hello, There is a really simple way to handle that even if it's not really pretty. You just have to surround you styles by ```js export const StyledButton = styled(Button)`...

i'm quite busy at the moment but if i could i take a look into this issue

I find these two issues related but i still have the problem : https://github.com/palantir/blueprint/issues/5111 https://github.com/palantir/blueprint/issues/3500

After reading `object` [ts reference](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-2.html#object-type) it might not be what you want to use here. Maybe ```ts typeof {} ``` or ```ts { [key:string]: any } ``` are more appropriate...

Here another example using basic `stack`property : https://codesandbox.io/s/distracted-vaughan-mxyyk6?file=/src/App.tsx

i have some doubt on the exact behaviour of the following type: ```ts export declare type PanelProps = P & PanelActions; ``` It may be an option to don't use...

If at some point you are looking to revamp/rewrite blueprintjs components with CSS-in-JS ii suggest using [styled-components](https://styled-components.com/) and [styled-system](https://styled-system.com/) If you added these it would be much easier to make...

I can't speak for other people but in my case the problem is not really related with Blueprint Component behaviour. It's pretty easy in fact to override Blueprint component even...

Hi there, I comment here in this issue because i get a lot of struggle with refs due to the fact their aren't forwarded (e.g: Card). It get better since...

any news on this ?