False positive ownership_invalid_binding?

[donghokimm]

Describe the bug

I've encountered the ownership_invalid_binding warning while working on a Svelte 5 project.

Reading the documentation was not helpful in fixing this issue.

Can you help me?

Reproduction

REPL

Logs

System Info

System:
  OS: Windows 11 10.0.26100
  CPU: (18) x64 Intel(R) Core(TM) Ultra 5 125H
  Memory: 4.40 GB / 15.74 GB
Binaries:
  Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
  npm: 10.9.0 - ~\AppData\Roaming\npm\npm.CMD
Browsers:
  Edge: Chromium (131.0.2903.99), ChromiumDev (133.0.3014.0)
  Internet Explorer: 11.0.26100.1882

Severity

annoyance

[dummdidumm]

The problem is that ownership is not widened correctly - it does not know about the previous owners because it's a class which is not traversed. For proxies we have logic in place for this, for classes we need something similar.

[mcullifer]

@dummdidumm So what would be the recommendation here? If we know the warning is due to it being class just ignore? Or do you recommend not using classes at all? I think I'm encountering a similar issue to this where I'm using a context which has a class as value. When child components get that context and mutate a property on the class I get the warning.

[dm-de]

This warning is confusing and useless.
I found out that it's all about where the value is changed. With snippets you can "bend" that - and the change takes place in other components.

see here:
#14145 (comment)

[donghokimm]

@dummdidumm
I appreciate the explanation!
Is there a plan to fix it?