Skip to content
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

Prop type conversion fails on custom element if attribute is not initialized on element #7096

Closed
misaacs21 opened this issue Nov 10, 2022 · 1 comment

Comments

@misaacs21
Copy link

misaacs21 commented Nov 10, 2022

Vue version

3.2.44

Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-8fqcef?file=src/components/MyCustomElement.ce.vue

Steps to reproduce

Click "Increment Page".

What is expected?

All "pages" and "page numbers" displayed on the page should be of type Number, and no warning should appear in console.

What is actually happening?

The custom element without attributes initialized does not convert the provided attribute values to Numbers. The following warnings appear in console:

[Vue warn]: Invalid prop: type check failed for prop "page". Expected Number with value 9, got String with value "9". 
  at <MyCustomElement title="Custom Element (do not init attrs)" pageNumber="9" page="9" >

[Vue warn]: Invalid prop: type check failed for prop "pageNumber". Expected Number with value 9, got String with value "9". 
  at <MyCustomElement title="Custom Element (do not init attrs)" pageNumber="9" page="9" >

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
npmPackages:
    vue: ^3.2.44 => 3.2.44

Any additional comments?

I ran into the same issue mentioned here, and after the fix was released in Vue v3.2.42, discovered type conversion still fails in the situation mentioned above.

@yyx990803
Copy link
Member

fixed via 89f37ce

Custom Elements Bugsquash automation moved this from Issues to Done Nov 11, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Sep 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants