fix: use displayName only for functional components

This fixes one of the issues that arise when bumping to vue 3.0.9. There is no change in behavior: it just make TypeScript OK with the recent changes in vue-next.
yakobe · Mar 29, 2021 · 5da353f · 5da353f
1 parent f6dd259
commit 5da353f
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/src/utils/find.ts b/src/utils/find.ts
@@ -36,9 +36,13 @@ export function matches(
     }
 
     let componentName: string | undefined
-    if ('name' in nodeType || 'displayName' in nodeType) {
-      // match normal component definitions or functional components
-      componentName = nodeType.name || nodeType.displayName
+    if ('name' in nodeType) {
+      // match normal component definitions
+      componentName = nodeType.name
+    }
+    if (!componentName && 'displayName' in nodeType) {
+      // match functional components
+      componentName = nodeType.displayName
     }
     let selectorName = selector.name