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: 58806ff9bc1baee43eb82b7cc23dcf69ad1233c4 🔍 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
iphydf
left a comment
There was a problem hiding this comment.
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