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

don't stop analyzing array, even if we already have a type and we can't create an object like #7093

Merged
merged 2 commits into from Dec 8, 2021

Conversation

orklah
Copy link
Collaborator

@orklah orklah commented Dec 7, 2021

The goal is to fix #7090

But seeing the change I had to do, it'll probably break something elsewhere, Let's run the CI!

@orklah
Copy link
Collaborator Author

orklah commented Dec 7, 2021

Well, that broke a test but in a goodish way.

the string part was ignored before so that's a fix. The weird thing is that mixed|string is usually simplified to mixed, that would make the test not broken. However, this seems on purpose because here:


We set the "allow_mixed_union" param to true in TypeCombiner. It does what it says and it allows mixed in unions. So, I fixed the test that way.

@orklah orklah added the release:fix The PR will be included in 'Fixes' section of the release notes label Dec 7, 2021
@orklah orklah merged commit eefdb95 into vimeo:master Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:fix The PR will be included in 'Fixes' section of the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong type combination: list<positive-int> + int = list<positive-int>
1 participant