Skip to content

Conversation

@amcasey
Copy link
Member

@amcasey amcasey commented Sep 13, 2017

It's not an issue because we'll just declare a corresponding type parameter on the extracted function and pass the original as a type argument.

Fixes #18142

Note that the first commit is actually #18423

@msftclas
Copy link

@amcasey,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@msftclas
Copy link

@amcasey,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

...for shorthand property assignment names when collecting usages.
@amcasey amcasey force-pushed the ExtractTypeParameter branch from e5eb1b0 to 80ec6fb Compare September 13, 2017 20:34
...correctly in a containing scope.  It's not an issue because we'll
just declare a corresponding type parameter on the extracted function
and pass the original as a type argument.

Fixes microsoft#18142
@amcasey amcasey merged commit 7b64229 into microsoft:master Sep 13, 2017
@amcasey amcasey deleted the ExtractTypeParameter branch September 13, 2017 23:42
amcasey added a commit to amcasey/TypeScript that referenced this pull request Sep 16, 2017
Stop preventing extraction when a type parameter wouldn't bind correctly in a containing scope

(cherry picked from commit 7b64229)
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants