Handling Restoring Fields with Errors #243
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe we should also handle the data with non existing keys. Currently the restoring ignores this data. There should an option for the user to check out old data and maybe use them for a existing key. |
pascalzauberzeug
approved these changes
Dec 2, 2024
pascalzauberzeug
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently fields that have incomplete or faulty data which may happen to updates in the code base, the fields are getting deleted and will not be stored again. We want to prevent this. When data is loaded from the persistence missing values should be replaced to a default value and the user should be getting informed by a notification to recheck the field's data.