eql can't handle circular references #98

Closed
jfirebaugh opened this Issue Sep 22, 2012 · 2 comments

Comments

Projects
None yet
3 participants
Owner

jfirebaugh commented Sep 22, 2012

This is something that Jasmine handles:

var circularObject = {};
var secondCircularObject = {};
circularObject.field = circularObject;
secondCircularObject.field = secondCircularObject;
expect(circularObject).to.eql(secondCircularObject);

Chai overflows the stack.

Owner

logicalparadox commented Oct 1, 2012

Does it just ignore circular references?
Does it check to ensure that the references are in both A & B are at to the same "path" of the original in order pass?

What are the suggested rules this should be handled by?

Contributor

domenic commented Nov 25, 2012

Looks like #104 got this?

domenic closed this Nov 25, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment