-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
The render function cannot render global components #1927
Comments
By the way, it works in template。 |
This is expected behavior in v3 Strings passed to |
In my human opinion, it should explicitly show on the Migration Guide Docs. |
@Fiv5 can you opeen a PR or an issue at vuejs/docs-next repository to track it? |
Sure, my pleasure! |
Is there an easy way to handle global components? // MyCustom.vue template
<div>
<el-xxxA /> // Globally registered
<el-xxxB /> // Globally registered
<div>
// App.vue
setup (props, content) {
const handleModify = (row) => {
ElMessageBox({
title: 'xxx',
message: h(MyCustom, { row: xxx })),
})
}
return {
handleModify
}
} Can you provide some parameters to resolve the global component?
|
Sometimes or just like:
The first param in the toast function may be a component, the usage like:
app.component('CompA', CompA);
app.component('CompB', CompB);
// ... If using some global register components in TIPS: The |
more detail: |
Version
3.0.0-rc.6
Reproduction link
https://codepen.io/dream2023/pen/QWNGQrM
Steps to reproduce
1.createApp
2.register component
What is expected?
Global components should be rendered
What is actually happening?
It's not rendered. It's just a tag name
The text was updated successfully, but these errors were encountered: