Repository navigation
feat(social): make follow operations idempotent (BA-052) - #1036
Open
ranjeetprabhatedu-dotcom wants to merge 1 commit into
Open
ranjeetprabhatedu-dotcom wants to merge 1 commit into
ranjeetprabhatedu-dotcom wants to merge 1 commit into
Conversation
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
1 participant
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
This PR addresses issue #965 (BA-052) by ensuring repeated follow requests do not create duplicate relationships or modify existing timestamps.
BackendAcademy/src/social/dto/follow.dto.ts: Added Swagger documentation toFollowDto.BackendAcademy/src/social/follow.service.ts: Added support for both parameter signatures and DTO objects infollowandunfollow, ensuring repeated follow operations are fully idempotent without side-effects or duplicate edges.BackendAcademy/src/social/follow.service.spec.ts: Added comprehensive unit test coverage verifying that repeated follow requests preserve edge uniqueness, counts, and existing timestamps, along with idempotent unfollow behavior.follow.service.spec.tspass cleanly (100% Green).Closes #965