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
chore: consider replacing any usage of any with unknown #59
Labels
chore
Make the code better
Comments
regevbr
changed the title
chode: consider replacing any usage of any with unknown
chore: consider replacing any usage of any with unknown
Apr 17, 2020
regevbr
added a commit
that referenced
this issue
Apr 17, 2020
regevbr
added a commit
that referenced
this issue
Apr 17, 2020
regevbr
added a commit
that referenced
this issue
Apr 17, 2020
regevbr
added a commit
that referenced
this issue
Apr 17, 2020
regevbr
added a commit
that referenced
this issue
Apr 18, 2020
regevbr
added a commit
that referenced
this issue
Apr 18, 2020
regevbr
added a commit
that referenced
this issue
Apr 18, 2020
regevbr
added a commit
that referenced
this issue
Apr 20, 2020
regevbr
added a commit
that referenced
this issue
Apr 20, 2020
regevbr
added a commit
that referenced
this issue
Apr 20, 2020
regevbr
added a commit
that referenced
this issue
Apr 20, 2020
ynahmany
added a commit
that referenced
this issue
Apr 23, 2020
regevbr
added a commit
that referenced
this issue
Apr 24, 2020
regevbr
added a commit
that referenced
this issue
Apr 24, 2020
regevbr
added a commit
that referenced
this issue
Apr 27, 2020
regevbr
added a commit
that referenced
this issue
Apr 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will enforce better type checking as the user of an unknown return type must use type guards before usage
The text was updated successfully, but these errors were encountered: