[🐞] [V2] destructuring props makes them Proxy all of a sudden

[omerman]

Which component is affected?

Qwik Runtime

Describe the bug

Version 2 is fantastic - Im about to open about 3 issues I found hope you address those I really want to merge my v2 product ;)

So issue 1: For some reason when passing props to a component, if I destructure the props, it becomes a proxy.
Its very hard to successfully explain it further.. You should get the idea by opening the small reproduction

This sort of thing did not happen in v1, although you could say it shouldnt matter.. well a 3rd party I use didnt like the proxied object and threw errors at me that took me some time to decipher 😅 If it is on purpose, then ok I will just not destructure as part of the render. But if its not on purpose, thought you might want to know its hapenning.

Let me know what you guys think,
Thanks ❤️

Reproduction

https://qwikdev-build-v2.qwik-8nx.pages.dev/playground/#f=7VdNT8JAEL37KyZc%2BEi7hCM1xJBw8qAHj8bDgq1tqKxh20DT7H%2F3zXZaihITNd7kQtOZHd7Ozr736A3NHMd3YWiCk%2Fr%2B0pWI3Gcv6ERXc1RvI3qsmZQimrknHqQfGxjEcUGOoBBYk2UC7VuB9fdlc%2F5gXg4sakBQuL5l7NoG9Z0PI7hqsH5RbHG2x1pquw%2BbrZEQkFJKO6yQJN5gN5SZXfpfQZt4GUEwKnkimk4abizSvYEdWccbjcYpRRKHBTtWYHC4KuilScia17hI2WjJEluUSQKlh%2FqkGqrBwm52eUUHcLdUKYxna35rU6gZZ0IlIDFS3q%2BybzmU1YJ24h0QrEA84PWtUlKlMiVt4OR0bg3lxmwJVYDFy0PrwyJJnkzloe%2FRBlkSokr4bMp1cT0eBPVQh4c026RhZkMdejjDiHRAvcCu6ALSXzTbDxF%2FZJB0v0m%2B302CA2SWt7bhks6iLQn85fw4tDBvH%2B7vVGNns6Qa1Q0cj%2BEGIE4HGgw7QKdw9%2BoTIjcOePw6EKzofhov8%2Bps3vvn8B1ePbu7%2F6z6F6z6Dg

Steps to reproduce

No response

System Info

-

Additional Information

No response

[wmertens]

Yes indeed this is on purpose as an optimization because we want to keep track of constant refs in props, so that we don't spend time checking props that never change.

So, thank you for the issue, but I'll close this as won't fix.

(BTW, you can do some autoformat by right-clicking and then "format document")

[omerman]

@wmertens I see - ok so its just because of the spreading as part of the destructuring right? because when I do this:
const {a, ...b} = prop a doesnt become a proxy, but b does.