This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Add type information that TSLint needs for some rules#25
Open
Add type information that TSLint needs for some rules#25
Conversation
Contributor
|
Heh :). I gave priority to |
unjapones
approved these changes
Jan 29, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This PR also disables some rules:
no-unnecessary-type-assertionwas giving a false positive in this line. There's an open issue here.completed-docsis annoying, do we really want docs for exported actions?promise-function-asyncadds unnecessary boilerplate, specially when dispatching async actions.