Open raveclassic opened 7 years ago
I don't use themr anymore, but when I did I used decorators.
You'll never be able to create good types for a decorator but you might be able to use what you now have but sill provide decorator support (with bad types) using a function overloads https://www.typescriptlang.org/docs/handbook/functions.html#overloads
If you publish your PR I can take a shot at it.
I need some time to actualize tests and migrate to latest TS 2.4.1
Currently I'm trying to rewrite
themr
in TS to provide consistent up-to-date typings and I'm in the middle of the struggle started in #39 The problem is that switching from correctReact.ComponentClass<P>
to component constructor type (withnew()
) is completely broken withstrictNullChecks
on, here's my commentMoreover, decorating a class with
@themr
complains on every lifecycle method (likecomponentWillMount
) of decorated class as TS can't cast it toComponentClass
. On the other hand, callingthemr
as a function on existing class works fine - seems like decorators are broken in TS. Well, at least they are still behind experimental flag.@mpodlasin @odensc Could you please check if you do use decorators instead of composing HOCs separately from actual component class or sfc which is more natural for react ecosystem in general especially when using recompose?
If it's ok for you and if it's worth dropping experimental decorators, I would open a PR with a fresh new
themr
fully in typescript.The good news are that now I'm finally able to overwrite props in decorated component with their non-necessary versions, thanks to this comment So that themed component does not require theme object to be passed via props but still checks its type if it is present.
UPDATE: still it will be possible and absolutely transparent to use themr as decorator for current ES6 users.