This prevents duplicate constructor instances when instances aren't directly bound, but are members of a list which is bound.
We saw this happening in Equibit and it made post-processing after loading items not work well (since an instance may have two or more copies, and the wrong one got the post-processing).
This PR is against the legacy 1.x versions of can-connect (CanJS 3.0 legacy), but after review, may also benefit the latest master branch as well.
This prevents duplicate constructor instances when instances aren't directly bound, but are members of a list which is bound.
We saw this happening in Equibit and it made post-processing after loading items not work well (since an instance may have two or more copies, and the wrong one got the post-processing).
This PR is against the legacy 1.x versions of can-connect (CanJS 3.0 legacy), but after review, may also benefit the latest master branch as well.