-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Provide a non-strict property check #17
base: master
Are you sure you want to change the base?
Conversation
When comparing big objects, it's hard to spot the actual property to see exactly where the difference is. There's probably a better way of printing the object, but this is a little workaround.
Hey, Samuel! Thanks for the PR! I think I set my time machine in the wrong direction and missed one year. :D Seems this is a related to #21. One idea I've had was to shorten the names of strict functions to have them use the What's your stance these days? |
Hi Andri, in general I try to avoid naming discussions, but I like your idea with the shorter names as in === vs ==. |
Too old now. Cleanup. |
Hey! I think your contribution is still worth looking at and I expect to do so. Thank you again! I'll keep this open, if you don't mind, as a reminder to do so when I eventually stop procrastinating. 😇 |
Sometimes I want to compare properties in a non-strict way, but would like to keep the notation.
Besides, I'd like to see the actual value of the property right away, hence the change in output for an AssertionError.