forked from AkkomaGang/akkoma
user: fix maybe_direct_follow() after user_info() refactoring broke it slightly
This commit is contained in:
parent
299ef74f2e
commit
1e9dd6fbc2
1 changed files with 2 additions and 2 deletions
|
@ -174,7 +174,7 @@ def maybe_direct_follow(%User{} = follower, %User{info: info} = followed) do
|
||||||
should_direct_follow =
|
should_direct_follow =
|
||||||
cond do
|
cond do
|
||||||
# if the account is locked, don't pre-create the relationship
|
# if the account is locked, don't pre-create the relationship
|
||||||
user_info["locked"] == true ->
|
user_info[:locked] == true ->
|
||||||
false
|
false
|
||||||
|
|
||||||
# if the users are blocking each other, we shouldn't even be here, but check for it anyway
|
# if the users are blocking each other, we shouldn't even be here, but check for it anyway
|
||||||
|
@ -193,7 +193,7 @@ def maybe_direct_follow(%User{} = follower, %User{info: info} = followed) do
|
||||||
if should_direct_follow do
|
if should_direct_follow do
|
||||||
follow(follower, followed)
|
follow(follower, followed)
|
||||||
else
|
else
|
||||||
follower
|
{:ok, follower}
|
||||||
end
|
end
|
||||||
end
|
end
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue