-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
fix(custom-element): preserve appContext during hmr reload #12455
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
base: main
Are you sure you want to change the base?
Conversation
Size ReportBundles
Usages
|
@vue/compiler-core
@vue/compiler-dom
@vue/compiler-ssr
@vue/compiler-sfc
@vue/reactivity
@vue/runtime-core
@vue/runtime-dom
@vue/server-renderer
@vue/shared
vue
@vue/compat
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no suggestions.
Comments skipped due to low confidence (1)
packages/runtime-dom/src/apiCustomElement.ts:524
- The new behavior introduced in the '_update' method should be covered by tests to ensure that 'vnode.appContext' is correctly set.
if (this._app && !this._instance) vnode.appContext = this._app._context
@edison1105 Can you tell me when this will be merged? Some colleagues and me would be very happy if the HMR works again for us 😅 |
@danieldasilva-smake npm i https://pkg.pr.new/vue@12455 It includes the latest code from the main branch. |
""" WalkthroughA new test case was added to verify that the provide context and global properties configured via Changes
Sequence Diagram(s)sequenceDiagram
participant TestRunner
participant CustomElement
participant VueApp
participant VNode
participant HMRRuntime
TestRunner->>CustomElement: Mount custom element with configureApp
CustomElement->>VueApp: Provide context and set global properties
CustomElement->>VNode: Create VNode and assign appContext
CustomElement->>VueApp: Render VNode
TestRunner->>HMRRuntime: Trigger HMR reload
HMRRuntime->>CustomElement: Reload component definition
CustomElement->>VNode: Create new VNode and assign appContext
CustomElement->>VueApp: Render new VNode
TestRunner->>CustomElement: Verify context and globals persist
Assessment against linked issues
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@@ -520,7 +520,9 @@ export class VueElement | |||
} | |||
|
|||
private _update() { | |||
render(this._createVNode(), this._root) | |||
const vnode = this._createVNode() | |||
if (this._app) vnode.appContext = this._app._context |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whether it's an HMR update or not, the appContext
needs to be preserved
close #12453
Summary by CodeRabbit
Bug Fixes
Tests