Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

turn on noImplicitAny #16

Closed
wants to merge 1 commit into from
Closed

turn on noImplicitAny #16

wants to merge 1 commit into from

Conversation

timruffles
Copy link

@timruffles timruffles commented Mar 31, 2017

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 🎉

Fixes #15.

Since this module is designed to be compiled by consumer projects (from what I can tell - see ngrx#15), it's nice to turn on noImplicitAny.

The compose function had a signature, but tsc didn't seem to be able to infer the argument types. I've added them, and checked that
`ComposeSignature` is still the type consumers see.

Fixes ngrx#15.
@timruffles
Copy link
Author

Closing as project seems quiet.

@timruffles timruffles closed this Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No implicit any errors
1 participant