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: findComponent in Suspense for rc.11 #206

Merged
merged 1 commit into from
Sep 17, 2020

Conversation

cexbrayat
Copy link
Member

vuejs/core#2099 introduced a big refactoring in how Suspense works, which broke VTU.
SuspenseBoundary no longer exposes the same interface, so our current implementation was not compiling anymore (and throwing at runtime).
This solves the issue and simplifies the current code, as the newly introduced activeBranch field now contains the... active branch of the Suspense, so we just have to check that.

vuejs/core#2099 introduced a big refactoring in how Suspense works, which broke VTU.
`SuspenseBoundary` no longer exposes the same interface, so our current implementation was not compiling anymore (and throwing at runtime).
This solves the issue and simplifies the current code, as the newly introduced `activeBranch` field now contains the... active branch of the Suspense, so we just have to check that.
Copy link
Member

@lmiller1990 lmiller1990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great catch. I will release a new version soon.

@lmiller1990 lmiller1990 merged commit 51ed47f into vuejs:master Sep 17, 2020
@cexbrayat cexbrayat deleted the chore/rc11 branch September 17, 2020 09:03
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.

2 participants