BUGFIX: fix support for stateful React components with TypeScript by making props mandatory #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WARNING: I'm a TS n00b, this is my first day with it.
Take a simple class-based react component and try to wrap it with themr:
You'd get an error:
This happens because themr defines props as optional where as
@type/react
defines it as mandatory:new (props: P, context?: any): Component<P, S>;
.