Skip to content
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

fix lookup regression again #26762

Merged
merged 2 commits into from
Aug 30, 2018
Merged

Conversation

Kingwl
Copy link
Contributor

@Kingwl Kingwl commented Aug 30, 2018

Fixes #26731

@RyanCavanaugh
Copy link
Member

@Kingwl thank you for the follow-up! Can you please add a testcase with the repro from the linked issue?

@ajafff
Copy link
Contributor

ajafff commented Aug 30, 2018

@RyanCavanaugh the baseline change is actually the same as my repro in the linked issue

@RyanCavanaugh
Copy link
Member

@ajafff true. I'd still prefer an explicit example - we are much more likely to notice an error file going from 0 to 1 or vice versa than a type baseline changing.

@Kingwl
Copy link
Contributor Author

Kingwl commented Aug 30, 2018

sure, wait a few moment

@sandersn
Copy link
Member

Thanks for the second fix @Kingwl.

@sandersn sandersn merged commit 038f665 into microsoft:master Aug 30, 2018
@Kingwl Kingwl deleted the fix_lookup_regression branch August 30, 2018 16:04
@Kingwl
Copy link
Contributor Author

Kingwl commented Aug 30, 2018

@sandersn
Actually, I hope there are nothing to fix. 🤷🏻‍♂️

RyanCavanaugh added a commit to RyanCavanaugh/TypeScript that referenced this pull request Aug 31, 2018
RyanCavanaugh added a commit to RyanCavanaugh/TypeScript that referenced this pull request Aug 31, 2018
…ration for a clean PR fixing all the issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants