Skip to content

typeRelatedToSomeType passes through intersectionState #43707

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

Merged
merged 2 commits into from
Apr 28, 2021

Conversation

sandersn
Copy link
Member

Previously it didn't, even though it should have.

eachTypeRelatedToSomeType still doesn't pass through intersectionState -- it just starts it off at None the way typeRelatedToSomeType did -- but I didn't change it on the grounds since I couldn't come up with a test case (this applies to any intersection excess property check, really).

Fixes #42715

Previously it didn't, even though it should have.
@sandersn sandersn self-assigned this Apr 16, 2021
@typescript-bot typescript-bot added Author: Team For Milestone Bug PRs that fix a bug with a specific milestone labels Apr 16, 2021
@sandersn sandersn merged commit db09cb5 into master Apr 28, 2021
@sandersn sandersn deleted the add-more-missed-intersectionState-parameters branch April 28, 2021 23:12
sandersn added a commit that referenced this pull request May 6, 2021
sandersn added a commit that referenced this pull request May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Author: Team For Milestone Bug PRs that fix a bug with a specific milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect excess property error when assigning to intersected array
3 participants