Closed BiggA94 closed 5 years ago
Initial investigations are that this should be fine -- it appears that those props are now just dealt with in tooling. Checking with some affected teams within MS to confirm.
We think it's going to be fine. Thanks for the contribution!
Nice, Thank you.
PS: Are version upgrades only triggered manually?
Published 1.1.0
short: Is there any reason, that P in https://github.com/Microsoft/ReSub/blob/467399dcbbd14fd264b9ef5a0a10f9d3acbf60c1/src/ComponentBase.ts#L44 extends React.Props instead of just {}, as the Component in the Typedefinition of React does?
See:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/cc6de05e3347a9ad3651df02f4b87603758e4398/types/react/index.d.ts#L397
Long form: I want to user Material-UI together with ReSub. Material-UI uses augmenting functions for the Properties. E.g.
So the Component would extend ComponentBase<Props, State>, but this gives a Compilation error, as in https://github.com/Microsoft/ReSub/issues/22. Extending React.props does only work, if on would leave the WithStyles augmentation. It adds the following:
Here, one would loose this convenience method..
The Official Types definition for React.Component (https://github.com/DefinitelyTyped/DefinitelyTyped/blob/cc6de05e3347a9ad3651df02f4b87603758e4398/types/react/index.d.ts#L397) defines the following:
Is there a particular Reason for having
instead of just
in https://github.com/Microsoft/ReSub/blob/467399dcbbd14fd264b9ef5a0a10f9d3acbf60c1/src/ComponentBase.ts#L44 ?