fix(server): addAssets and removeAssets handle duplicate assetIds #9436
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 #9368, where calling
addAssets
with duplicate ids results in an internal server error.This fix leverages the
existingAssetIds
Set already included inaddAssets
, but I could see the argument that we should keep that reserved for assets that were in the database before callingaddAssets
. If you feel that way I can instead revise this to create a dedicated Set just for uniqueness withinaddAssets
.Input:
Output:
Before:
After:
For consistency, I also made the corresponding change in
removeAssets
. In my opinion the output from this change is more accurate/helpful, but let me know if you disagree.Input:
Output:
Before:
After: