fix(runtime-core): fix component name inference in warnings

Should not pollute component definition name property
fix #1418
This commit is contained in:
Evan You
2020-06-26 09:28:15 -04:00
parent 1c4e1b6792
commit e765d81404
4 changed files with 24 additions and 20 deletions

View File

@@ -48,7 +48,9 @@ export function warn(msg: string, ...args: any[]) {
msg + args.join(''),
instance && instance.proxy,
trace
.map(({ vnode }) => `at <${formatComponentName(vnode.type)}>`)
.map(
({ vnode }) => `at <${formatComponentName(instance, vnode.type)}>`
)
.join('\n'),
trace
]
@@ -109,7 +111,11 @@ function formatTraceEntry({ vnode, recurseCount }: TraceEntry): any[] {
const postfix =
recurseCount > 0 ? `... (${recurseCount} recursive calls)` : ``
const isRoot = vnode.component ? vnode.component.parent == null : false
const open = ` at <${formatComponentName(vnode.type, isRoot)}`
const open = ` at <${formatComponentName(
vnode.component,
vnode.type,
isRoot
)}`
const close = `>` + postfix
return vnode.props
? [open, ...formatProps(vnode.props), close]