-
Notifications
You must be signed in to change notification settings - Fork 292
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
chore: tox_new() should return null when savedata loading fails #1944
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1944 +/- ##
==========================================
+ Coverage 74.41% 74.51% +0.10%
==========================================
Files 87 87
Lines 26235 26241 +6
==========================================
+ Hits 19523 19554 +31
+ Misses 6712 6687 -25 ☔ View full report in Codecov by Sentry. |
cfca43d
to
2b89506
Compare
✔️ Deploy Preview for c-toxcore ready! 🔨 Explore the source changes: 58806ff 🔍 Inspect the deploy log: https://app.netlify.com/sites/c-toxcore/deploys/620dbd3d5a7e34000a1e82b7 😎 Browse the preview: https://deploy-preview-1944--c-toxcore.netlify.app |
8f7c3a2
to
a36e24f
Compare
10e1aed
to
58806ff
Compare
57e4dc8
to
e6af91b
Compare
Maybe it is. It probably makes sense to be a bit lenient with slightly broken savedatas. |
Ok, I've changed my mind. However, I think that the loading code should be quite accepting, and return CONTINUE more often, and only return ERROR if the error is not recoverable. That can be done later, though. |
5efeb8a
to
17282e7
Compare
Returning a valid tox instance when loading a corrupt savefile is probably not desired behaviour
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.
Reviewed 2 of 2 files at r1.
Reviewable status: complete! 1 of 1 approvals obtained
Returning a valid tox instance when loading a corrupt savefile is probably not desired behaviour
This change is