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
{{ message }}
This repository has been archived by the owner on Jan 11, 2018. It is now read-only.
via inheritance -> instead of class extends Component<any> --> class extends Disabled
classColoredAndDisabledextendsComponent<Props>{staticgetprops(){return{disabled: prop.boolean(),color: prop.string(),}}color: ColorType;disabled: boolean;}classButtonextendsColoredAndDisabled{
@propghost: boolean;
@propblock: boolean;// no redeclare needed :) ! but this is not composable - because how inheritance works}
this is very unfortunate indeed ( limitation of Typescript - it works ofc within Vanilla JS.
There is one last hope - to try define mixins via our custom @prop decorator TODO @Hotell
Expected behavior
bump to stable latest TSC and resolve issues
The text was updated successfully, but these errors were encountered:
Current behavior
We are using RC which doesn't work as it should.
There are important errors with stable branch ( when used for mixins )
se related issue microsoft/TypeScript#338 (comment)
So as it turns out, at this moment we have 2 options how to reuse property definitions etc:
class extends Component<any>
-->class extends Disabled
this is very unfortunate indeed ( limitation of Typescript - it works ofc within Vanilla JS.
There is one last hope - to try define mixins via our custom
@prop
decorator TODO @HotellExpected behavior
bump to stable latest TSC and resolve issues
The text was updated successfully, but these errors were encountered: