-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add null check to verifyIfObjectsMatch #58
Add null check to verifyIfObjectsMatch #58
Conversation
hi @baruchvlz , kindly look into PR. It will help the cypress community in a way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @tobloef, thanks for looking into this. For me, this is an odd bug since the verify
has a default value in the function. As long as the test pass I'm ok with the change.
Thanks. As far as I know, the default value is only used if the passed argument is |
Tried to update it based on your feedback. Let me know what you think. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove semi-colons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking care of this. I will do a release later today.
@baruchvlz do we have a new release yet? thanks. |
@abhinaba-ghosh @tobloef I'm really sorry y'all, completely slipped my mind to publish the package. v1.8.0 should be available now. |
Thanks a lot. 😇 |
This was causing some trouble for me. To give some context, I encountered this in my Cypress tests using cypress-react-selector, which is dependent on resq. I'm not sure exactly what is causing the argument to be null, but this seemed like the easiest fix.