Follow/Unfollow fixed #92
Merged
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
cengique
approved these changes
Mar 30, 2025
Member
cengique
left a comment
cengique
left a comment
There was a problem hiding this comment.
Works as intended and fixes the previous wrong logic.
cengique
pushed a commit
that referenced
this pull request
Mar 30, 2025
Fixed conflicts caused by merging #92.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Corrected the logic in the follow and unfollow endpoints to reflect the intended follower relationship accurately:
(Note: The current implementation in the develop branch incorrectly handles the follow/unfollow logic. Specifically, it reversed the relationship between the follower and the user being followed)