Fix restore after export #1274
Merged
Fix restore after export #1274
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
mkondratek
changed the title
mkondratek
changed the title
pkukielka
reviewed
Apr 3, 2024
| @@ -40,6 +41,7 @@ class ExportChatsBackgroundable( | |||
| .filter { it.internalId != null } | |||
| .filter { chat -> if (internalId != null) chat.internalId == internalId else true } | |||
|
|
|||
| var dummyInternalId = UUID.randomUUID().toString() | |||
There was a problem hiding this comment.
Does it also work for restore all?
Or, in other words, we just need one dummyInternalId or one per restored chat?
There was a problem hiding this comment.
we need one per chat and that's what I do here (see line 58)
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.
Fixes #1247.
It could be a temporary solution to the original problem. The ideal solution is to make chat restore idempotent.
Test plan