Updated GraphQL operations to support efficient follow status checking:
- Added isFollowedByCurrentUser field to UserSocialsFields fragment
- Removed nested followers array from UserSocialsFields (over-fetching)
- Simplified followUser/unfollowUser mutations to return minimal data
- Added hasFollowing field to GetVideoFeed query for feed mode detection
- Updated getUserFollowingFollowers query to include isFollowedByCurrentUser
These changes enable the mobile app to:
- Display correct follow/unfollow button states without client-side lookups
- Differentiate between "Following" and "Popular" feed modes
- Reduce payload size by removing unnecessary nested data
Backend handles efficient resolution via request-scoped caching.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
currently will select first item if multiple tags present for a given class
if we want to change the UI I can make it process & display multiple values for gameTypes/tableSizes, but as of now it's meant to handle a single one
CLOSES#288
Co-authored-by: Loewy <loewy@chainstarters.com>
Reviewed-on: railbird/railbird-mobile#293
Reviewed-by: Ivan Malison <ivanmalison@gmail.com>
