gh-133: Add strict on BE #144
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
littlewhywhat
force-pushed
the
133-no-implicit-any
branch
3 times, most recently
from
01a36e5 to
3365a31
Compare
littlewhywhat
force-pushed
the
133-no-implicit-any
branch
from
3365a31 to
9a5987d
Compare
littlewhywhat
changed the title
littlewhywhat
requested review from
novellizator and
petrk-salsita
as code owners
littlewhywhat
force-pushed
the
133-no-implicit-any
branch
from
a876918 to
6122ad4
Compare
littlewhywhat
force-pushed
the
133-no-implicit-any
branch
from
6122ad4 to
e613ace
Compare
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.
Closes gh-133
Eventually adding strict :)