You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could potentially be solved by keeping track of every object traversed and never checking the structure of it again, once it has been traversed. This will stop any kind of circular reference from overflowing the stack during equalTo() matching.
oneronaut
changed the title
Add a matcher that traverses ContentNodes...
equalTo() matcher to avoid circular references
Feb 12, 2018
requirement: Stop the
equalTo()
matcher from traversing any object it has already traversed during the match.driver: This will stop it from overflowing the stack when an object being checked contains a circular reference.
The text was updated successfully, but these errors were encountered: