Skip to content

fix(devtools-kit): only treat own render property as component definition#1110

Open
lazerg wants to merge 1 commit into
vuejs:mainfrom
lazerg:fix/pinia-unknown-component
Open

fix(devtools-kit): only treat own render property as component definition#1110
lazerg wants to merge 1 commit into
vuejs:mainfrom
lazerg:fix/pinia-unknown-component

Conversation

@lazerg

@lazerg lazerg commented Jul 2, 2026

Copy link
Copy Markdown

Fixes #1100.

As @skirtles-code pointed out in the issue, the state serializer treats any object with a render method as a Vue component definition, so plain class instances stored in Pinia state (whose class happens to define a render method) are shown as "Unknown component". A component definition keeps render as an own property, whereas a class instance inherits it from the prototype, so this checks for an own render property — real component definitions are still detected, and ordinary objects are left alone.

@netlify

netlify Bot commented Jul 2, 2026

Copy link
Copy Markdown

Deploy Preview for vue-devtools-docs canceled.

Name Link
🔨 Latest commit 28eb839
🔍 Latest deploy log https://app.netlify.com/projects/vue-devtools-docs/deploys/6a46b2ef763efb00086cdf79

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.

"Unknown component" in Pinia devtools

1 participant