-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bigint does not display correctly in Command Log, throws error on print to console of 0n #16570
Comments
Our code tries to run lodash I'm not sure exactly why it displays as We would accept a pull request to fix the display and error. |
|
The code for this is done in cypress-io/cypress#16640, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
There are currently two issues with bigint in cypress.
{}
instead of serializing the bigint. If you click on the assertion, it displays properly in the console:0n
, you get an exception when you click on it:Desired behavior
0n
on expected or actual, no exception should occurTest code to reproduce
Versions
This is present in 5.6.0 through 7.3.0, though you get different behavior for the exception in 5.6.0 and 7.3.0. In older versions, it doesn't show the exception and stack trace, but expected/actual are missing:
The text was updated successfully, but these errors were encountered: