Do not get the apparent type for 'getContextualType' in the services layer#5615
Merged
DanielRosenwasser merged 2 commits intomasterfrom Nov 11, 2015
Merged
Do not get the apparent type for 'getContextualType' in the services layer#5615DanielRosenwasser merged 2 commits intomasterfrom
DanielRosenwasser merged 2 commits intomasterfrom
Conversation
DanielRosenwasser
added
the
Breaking Change
Contributor
|
Can you add a test here. something where the apparent type would be needed to find all refs. e.g. a generic type argument constraint, and find all refs on an object literal contextually typed by it. |
DanielRosenwasser
added a commit
that referenced
this pull request
Nov 11, 2015
Do not get the apparent type for 'getContextualType' in the services layer
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.
See relevant discussion starting from #5602 (comment)
This doesn't seem to affect any of our tests in the services layer, so I don't think this is a major break.