TrackDAO::saveTrack(): Return success/failure result #4603
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
|
The biggest refactoring affects TrackCollectionManager::saveTrack() were the 2 cases are now clearly separated from each other in a linear fashion. The 1st case (purge) actually only catches a very rare potential race condition. |
Swiftb0y
reviewed
Jan 6, 2022
Holzhaus
approved these changes
Jan 6, 2022
|
Ping |
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.
A straightforward refactoring to simplify the code. Makes the control and data flow explicit instead of implicitly relying on the result of side effects.
Boolean value because it is only an internal API.