[1.x] Fix reactivity conflict caused by Object.prototype.hasOwnProperty

[Tofandel]

Fixes #34

[saibotk]

Looks good to me thank you very much!

Can you fix the eslint warnings ans add some ignores for the hasOwnProperty usage with a comment that this is to allow reactivity?

Oh and quickly add a line to the Changelog and we are ready to merge

[Tofandel]

Done

[djfhe]

Hi, thanks for looking into this!
I suggest an alternative solution to avoid any security risks while still fixing it.

Let me here your thoughts on this!

[djfhe]

Suggested change

	// eslint-disable-next-line no-prototype-builtins
	!current?.hasOwnProperty(pathPart) // We use the builtin to avoid reactivity issues with Proxy
	current === null ||
	current[pathPart] === undefined || // Trigger dependency tracking for libraries (e.g. vue)
	!hasOwnProperty.call(current, pathPart)

I would suggest this. We still use the global hasOwnProperty function but signal vue, that we access the property so its depedency tracking works.

[djfhe]

Suggested change

	// eslint-disable-next-line no-prototype-builtins
	!current?.hasOwnProperty(pathPart)
	current === null ||
	current[pathPart] === undefined || // Trigger dependency tracking for libraries (e.g. vue)
	!hasOwnProperty.call(current, pathPart)

The same here. Adding this undefined check should not change behavior, since the check in line 292 would have catched the undefined parentObject otherwise.

[Tofandel]

This seems like a good alternative, I see that you already released it, so I will close this