FlxSave: Allow custom handling of parsing errors #3286
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a
backupParser
arg tobind
, which is called to handle parsing errors, also addsFlxSaveStatus.LOAD_ERROR
which is an error that happened during the bind (load) process, where ERROR happened during the flush (save) process that was not resolved.Alternative to #3270, any thoughts @EliteMasterEric ?
When the load error is a parsing error, the raw save data and parsing exception are available in the save's state. To repair the save, manually edit and/or unserialize it, wipe the old save and replace it with the new, repaired data
Example