-
Notifications
You must be signed in to change notification settings - Fork 204
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
fix(proofs): await shouldAutoRespond to correctly handle the check #1116
fix(proofs): await shouldAutoRespond to correctly handle the check #1116
Conversation
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.
🔥
Just a little edit on the scope for changelog ("proofs" instead of "proof")
@TimoGlastra Would it be possible to get this in 0.3.0? I assume if it goes to main now it will be in 0.3.0, right? |
We are working on 0.3.0.alpha.xxx, so every commit will be included to the 0.3.0 release. A new PR will be created later on (I think Timo created the current release PR just to help me on the migration guide, as it generates the changelog). |
Yes I think we should add no-floating-promises and no-misused-promises |
Codecov Report
@@ Coverage Diff @@
## main #1116 +/- ##
==========================================
- Coverage 88.28% 88.16% -0.13%
==========================================
Files 705 705
Lines 16399 16405 +6
Branches 2657 2657
==========================================
- Hits 14478 14463 -15
- Misses 1914 1935 +21
Partials 7 7
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Apparently the tests were written for the incorrect way of doing autoAccept. Will fix this ASAP tomorrow. |
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
af00bb0
to
9187e59
Compare
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
Sorry that it took so long, the bug was a bit bigger than just a missing "await". Our deep equality check did not work, and I had to change it. (also added some more tests to be sure). |
Signed-off-by: blu3beri <[email protected]>
Signed-off-by: blu3beri <[email protected]>
I forgot auto merge was enabled. @TimoGlastra @genaris if you see something wrong, I will revert the pr. |
We did not await the
shouldAutoRespondTo...
and if we then check if the value is truthy, it is because it is a Promise and not the contained value ofboolean
.Abstracting the async function call to a variable above makes an IDE error on the if statement is it will always be truthy if not-awaited.
@TimoGlastra Would it make sense to add a rule that you must mark void/await for async calls? that would've probably avoided this, quite big, bug.
closes #1095