Disable evolving types with implicit any#12362
Merged
Uh oh!
There was an error while loading. Please reload this page.
Conversation
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
That is, without --noImplicitAny
MemberAuthor
sandersn commented Nov 18, 2016
@mhegazy@ahejlsberg I disabled evolving types when |
MemberAuthor
sandersn commented Nov 18, 2016
@mhegazy thanks for the reminder to always leave evolving types on for Javascript files. |
mhegazy approved these changes Nov 18, 2016
Contributor
mhegazy commented Nov 18, 2016
We will need to port this to release-2.1 as well. |
MemberAuthor
sandersn commented Nov 18, 2016
Done |
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
Fixes#11839