Activate TypeScript's noImplicitAny rule
#752
Merged
Conversation
This file contains 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
Acconut
changed the title
noImplicitAny rulenoImplicitAny rule
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 actives the
noImplicitAnyrule from TypeScript and fills in the missing type annotations. One noteworthy change in the API is thatSliceResultnow has an explicitsizeproperty: https://github.com/tus/tus-js-client/compare/no-implicit-any?expand=1#diff-7aa514e8766689bfea8a2264cb7dfc9140125a8b34e7eb5876b542ed6e1b3addR105 This was previously not the case, but now every slice operation must return the number of bytes present in its returned, opaque value.