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: support type narrowing for components #3350

Merged
merged 5 commits into from Jul 5, 2023

Conversation

so1ve
Copy link
Member

@so1ve so1ve commented Jul 2, 2023

closes #3138

@so1ve so1ve marked this pull request as draft July 2, 2023 14:48
@so1ve
Copy link
Member Author

so1ve commented Jul 2, 2023

I have to discard the changes in workflow file :(

@rchl
Copy link
Collaborator

rchl commented Jul 2, 2023

I think you just need to run pnpm i to update the lock file to fix the CI.

@so1ve
Copy link
Member Author

so1ve commented Jul 2, 2023

I think you just need to run pnpm i to update the lock file to fix the CI.

Yes, you are 100% right :)

However Johnson didn't update the lockfile in master branch, so we may push to master directly.

And I changed the workflow file by accident, I need to revert that later :(

@rchl
Copy link
Collaborator

rchl commented Jul 2, 2023

I see that your workflow changes change line endings from Windows to Unix which seems like a good change overall but probably should be done separately.
(test.yml workflow is also using Windows line-endings)

@rchl
Copy link
Collaborator

rchl commented Jul 2, 2023

BTW. I don't have access to be able to push to master but if you do then I suppose it might be a good idea.
Or otherwise we could create a separate PR that does just that.

@rchl
Copy link
Collaborator

rchl commented Jul 2, 2023

fixing ci in #3352

@so1ve
Copy link
Member Author

so1ve commented Jul 2, 2023

BTW. I don't have access to be able to push to master but if you do then I suppose it might be a good idea. Or otherwise we could create a separate PR that does just that.

I have the access to, but I think pushing directly without Johnson's permission is not a good idea. If you are interested, could you please help me revert the changes made to workflow file? (I'm unable to code now, but I can do this tomorrow) Thanks a lot!

@rchl
Copy link
Collaborator

rchl commented Jul 2, 2023

I don't have write access to the repo so I can't help directly but you should be able to just merge master into your branch and those changes should go away.

@so1ve so1ve marked this pull request as ready for review July 3, 2023 04:30
@johnsoncodehk johnsoncodehk changed the title fix: fallback to __VLS_ctx if component is not found in __VLS_templateComponents fix: support type narrowing for components Jul 5, 2023
@johnsoncodehk johnsoncodehk merged commit cefbaff into vuejs:master Jul 5, 2023
3 checks passed
@so1ve so1ve deleted the fix/issue-3138 branch July 5, 2023 03:18
@johnsoncodehk
Copy link
Member

johnsoncodehk commented Jul 5, 2023

@rchl I added write permissions to you, in case we get hit by a bus.

@rchl
Copy link
Collaborator

rchl commented Jul 5, 2023

I hope not :)
I won't have much time to help but thanks for that.

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.

TS2345: Argument of type '{}' is not assignable to parameter of type 'never'
3 participants