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
Removing the $maxDepth parameter from assertEquals() etc. will break all tests that use assertEquals() with optional parameters that go after $maxDepth.
The only way to clean up assertEquals() that {hopefully|possibly} causes less problems would be to clean up more drastically and not only remove $maxDepth but also all optional parameters that come after it. This, too, is not really appealling.
All these optional parameters should have never been added, they make for a terrible API. I am not sure, though, if the benefit of cleaning up assertEquals() etc. by removing these optional parameters and adding more specific assertion methods in their stead outweighs the pain of breaking compatibility.
Moved here from #3335 (comment).
The text was updated successfully, but these errors were encountered: