aboutsummaryrefslogtreecommitdiff
path: root/src/services/entity_normalizer/entity_normalizer.service.js
diff options
context:
space:
mode:
authorrinpatch <rinpatch@sdf.org>2019-08-09 14:18:46 +0300
committerrinpatch <rinpatch@sdf.org>2019-08-09 15:01:13 +0300
commit766bcc2a72bc9e6966c0ce174d1887ac6b8cc5c4 (patch)
tree736798809364866aad8caed0de9a1aa9fd6189e5 /src/services/entity_normalizer/entity_normalizer.service.js
parenta45f258a2cc5048f4839bee575d7754673189576 (diff)
Fix sent follow request detection
This fixes `requestFollow` using the relationship instead of user object, resulting in `sent` always being false for locked users, and also removes assumptions about follow request being sent, instead relying on `requested` from user relationship.
Diffstat (limited to 'src/services/entity_normalizer/entity_normalizer.service.js')
-rw-r--r--src/services/entity_normalizer/entity_normalizer.service.js1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/services/entity_normalizer/entity_normalizer.service.js b/src/services/entity_normalizer/entity_normalizer.service.js
index c8474302..6cc1851d 100644
--- a/src/services/entity_normalizer/entity_normalizer.service.js
+++ b/src/services/entity_normalizer/entity_normalizer.service.js
@@ -65,6 +65,7 @@ export const parseUser = (data) => {
if (relationship) {
output.follows_you = relationship.followed_by
+ output.requested = relationship.requested
output.following = relationship.following
output.statusnet_blocking = relationship.blocking
output.muted = relationship.muting