can-connect
can-connect copied to clipboard
Maximum call stack if two instances without id are created (can/constructor-hydrate)
When using can/constructor-hydrate/constructor-hydrate behaviour and trying to create two instances without an id, we get into an infinite loop.
Also notice that connection's instanceStore contains an item with a key undefined.
@ilyavf what does this look like?