Since this module is designed to be compiled by consumer projects (from what I can tell - see #15), it's nice to turn on noImplicitAny so those using noImplicitAny don't suffer compiler warnings.
The compose function had a signature, but tsc didn't seem to be able to infer its argument types so considers them implicitly any. I've added annotations, and checked that ComposeSignature is still the type consumers see.
I'm now using this commit in my project, and the compiler warnings have thankfully ceased 🎉
Since this module is designed to be compiled by consumer projects (from what I can tell - see #15), it's nice to turn on
noImplicitAny
so those usingnoImplicitAny
don't suffer compiler warnings.The compose function had a signature, but
tsc
didn't seem to be able to infer its argument types so considers them implicitly any. I've added annotations, and checked thatComposeSignature
is still the type consumers see.I'm now using this commit in my project, and the compiler warnings have thankfully ceased 🎉
Fixes #15.