Ref accessed via Object.prototype.hasOwnProperty.call isn't traced in computed

[leoleoasd]

Vue version

3.3.4

Link to minimal reproduction

https://play.vuejs.org/#eNp9VNtu4jAQ/ZVRXpJsUYD2jYZqL6q0u9pdqm3fcFWFxICpsS1fKBXKv+/YIRC2tDyQeObM8ZnjcXbRF6WyjaPRKMpNqZmyYKh1CnghFmMSWUOiGyLYWkltYQeazntQyrVyllZQw1zLNcRIEBNBRCmFsVCx0sLYQ5MdEQDxMB5dElGn1y2iJfj+8PsXIttlkqQwvoFQ5EmyTcEdxSoATi0SetrpYwjMpU58kGFocI2PHIaDAb5dXABLAwUAm0Myma0oUiktrbSvimbLwkxexJ2Wimr7mpUF58lxtx6wzMp7q5lYJGmaNmr8D7fPlDPLDnjaxT4C7gyfvAzfqS+p/SP8YbHTInCsJBNJ3IvTE0tQX9DzVEonWvsuj/miqp5aDGY7Tu0bLIxhC3HSyV769JS7yXaFj2AYhDayz6HhYgxDzNbHI1zigNB3JHUcwsNHY/bVQETeb8YMhwoXlq4VLyzFFUBesU14AdjtPEUdrMPETB/i3dF5m89nzlop4HPJWfmM89u1DScZl4f+8n4Dfq/0vw6xuomcJ8j7jfq8f+gp6uH1QbfmbJGtjBR4x4I7SI1NME71RFmGbpJo1J4VKuZcvvwMMavxFNt4uaTl85n4ymx9jER3mhqqN5REh5wt9ILaJn17/4du8f2QXMvKcUR/kPxLjeTOa2xgX52oUHYHF9T+CF8HnKUHc7u1VJi2KS80TFbAkwi/E98+aP0o9yq72l+dOqr/AW3XiqU=

Steps to reproduce

1. create a ref
2. in a computed, call Object.prototype.hasOwnProperty.call
3. add a new property to the ref's value
4. computed isn't updated.

What is expected?

add_property also updates the computed

What is actually happening?

only change_property does

System Info

No response

Any additional comments?

The "create issue" button in https://new-issue.vuejs.org/ isn't working; github is asking me to filling the issue template AGAIN.

[leoleoasd]

Is there anyway to tell the runtime tracer that ALL of the property, including NEW ones are used in computed?

[leoleoasd]

I don't know why, but adding console.log(dict.value); helps in vue sfc playground, but doesn't work with vite development server (just create a fresh new vite project and paste the exact code there).
SFC Playground:

Vite:

[chenfan0]

before

if (Object.prototype.hasOwnProperty.call(dict.value, i.toString())) {
      ret.push(dict.value[i.toString()] + i * 100);
}

after

 if (dict.value.hasOwnProperty(i.toString())) {
      ret.push(dict.value[i.toString()] + i * 100);
 }

You can directly use dict.value.hasOwnProperty to solve this problem

[leoleoasd]

Thanks!
Then I guess the rest of the problem is:

1. Is this a bug, or it isn't fixable? Is this guranteed in vue's reactivity?
2. If this isn't a bug, should this be documented in somewhere like here? Will other Object.prototype.xxxxx work? I vaguely remembered that vue can't track dynamically added properties (back in vue2) and I googled for this behavior for hours and got nothing.

[chenfan0]

object.hasOwnProperty works normally because vue handles it internally

You can also solve this problem by setting a new object to dict.value

[chenfan0]

You can see this PR for some detailed information。#2621

[leoleoasd]

Thank you @chenfan0. Now I understand why this doesn't work.
However, SHOULD this work? Is current behavior considered a bug?

1. If it should work, we should fix this
2. If it shouldn't work (i.e. a 'feature' rather than a 'bug'), we should clarify this in the documentation (like in the FAQ section of reactivity page).