-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
assert: --assert-full-diff #52921
assert: --assert-full-diff #52921
Conversation
i'd rather we add an options object to |
I'm worried that users may misunderstand the options object for an object to be asserted |
The commit message does not adhere to the guidelines, the tests are not passing: I'm converting this PR to draft. I think you can that reviewing PRs takes time, and as it is currently it doesn't seem like reviewing this PR would be a good use of my time. Sorry if my comment sounds dismissive, I know you spent time making this PR, and I would prefer show more respect of that time you spend, but honestly I don't feel that you sending this PR as is is very respectful of the reviewers' time either. |
No problem! I'll fix the PR and verify everything before I resubmit
I'm sorry, I'll fix the PR, I didn't realize it was failing the tests (sorry!). |
ac2e677
to
2a0ae9b
Compare
(forgot to un-draft this)
|
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.
We should aim for rewriting assert to a class to add options instead of using flags to define the output behavior. That would allow to add even more options that would be useful.
I do understand that mostly all assertions should be handled identically, but using a flag for that behavior seems unintuitive for me.
Can this land (once conflicts are resolved), or is it not even worth it? |
Fixes #51902
This PR adds a
--assert-full-diff
option to have AssertionErrors print the full diff, rather than a truncated version.