fix: save call history log entries for both caller and receiver#71
Merged
Conversation
|
✅ PR Validation Passed Your PR title and description meet all requirements:
|
This file contains hidden or 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
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.
Summary
Fixes an issue where call history was only visible to the participant who triggered the log creation (typically the caller or whoever hung up). The endpoint now writes two mirrored entries to the database simultaneously so that both participants have the call registered in their personal history logs.
Related issue
Fixes #70
Changes
CallLog.create()invocation withCallLog.insertMany()to atomically create logs for both users.mirrorType(swappingoutgoing↔incoming) for the receiving participant.Testing
/api/calls/logs.outgoingtype log and the receiver has anincomingtype log.Checklist
Fixes #70