Skip to content

Only skip following inference steps after union member matching if an inference is actually made #33154

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

Conversation

weswigham
Copy link
Member

Fixes #33131

I'm not sure if you'd like to reconsider more here, but, generally speaking, this seems like a fairly minimal tweak to the logic we added to better match union/intersection types that un-breaks rxjs with only a minimal (and arguably beneficial) change to our own baselines.

@weswigham
Copy link
Member Author

@typescript-bot test this
@typescript-bot user test this
@typescript-bot run dt

@typescript-bot
Copy link
Collaborator

typescript-bot commented Aug 29, 2019

Heya @weswigham, I've started to run the extended test suite on this PR at 737d1e7. You can monitor the build here. It should now contribute to this PR's status checks.

@typescript-bot
Copy link
Collaborator

typescript-bot commented Aug 29, 2019

Heya @weswigham, I've started to run the parallelized Definitely Typed test suite on this PR at 737d1e7. You can monitor the build here. It should now contribute to this PR's status checks.

@typescript-bot
Copy link
Collaborator

typescript-bot commented Aug 29, 2019

Heya @weswigham, I've started to run the parallelized community code test suite on this PR at 737d1e7. You can monitor the build here. It should now contribute to this PR's status checks.

@typescript-bot
Copy link
Collaborator

The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master.

@weswigham
Copy link
Member Author

I think this fixes an issue in the azure sdk. Or they fixed one since my last result and for the fourth time today, again the user baselines are just today's as yet uncaptured/accepted update (just changes in upstream projects), and thus are clean~

@weswigham
Copy link
Member Author

Also removes an error in RWC of the form Argument of type '{ [name: string]: unknown; }' is not assignable to parameter of type '{ [name: string]: string | number; }', which seems like a fix to me.

@weswigham
Copy link
Member Author

The two DT changes are related, and I need to look at the lodash one in detail, but I think the new handful of results are probably just as good if not better than the old ones.

@typescript-bot pack this for posterity. And testing.

@benlesh does this fixup inference in all of rxjs?

@typescript-bot
Copy link
Collaborator

typescript-bot commented Aug 30, 2019

Heya @weswigham, I've started to run the tarball bundle task on this PR at 737d1e7. You can monitor the build here. It should now contribute to this PR's status checks.

@typescript-bot
Copy link
Collaborator

Hey @weswigham, I've packed this into an installable tgz. You can install it for testing by referencing it in your package.json like so:

{
    "devDependencies": {
        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/42167/artifacts?artifactName=tgz&fileId=84FA9BD7390E9AE04ED6006D9E265FBCF309C643377CBBC8CB1CE445229AAB2B02&fileName=/typescript-3.7.0-insiders.20190830.tgz"
    }
}

and then running npm install.

@weswigham
Copy link
Member Author

@ahejlsberg has an alternative implementation he'll have a PR up for shortly

@weswigham weswigham closed this Sep 4, 2019
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.

RxJS type inference fails in 3.6.2
3 participants