aboutsummaryrefslogtreecommitdiff
path: root/test/web
diff options
context:
space:
mode:
authorrinpatch <rinpatch@sdf.org>2020-04-11 21:44:52 +0300
committerrinpatch <rinpatch@sdf.org>2020-04-11 22:31:46 +0300
commitc077ad0b3305e74f5b8d1b9bf38d4f480d76c1a6 (patch)
treeeb702217459d29b86cbbaecf48e5547729d82152 /test/web
parentfc4f92c5de54f4a427fb0fccbd4e64a72344ac6f (diff)
downloadpleroma-c077ad0b3305e74f5b8d1b9bf38d4f480d76c1a6.tar.gz
Remove User.upgrade_changeset in favor of remote_user_creation
The two changesets had the same purpose, yet some changes were updated in one, but not the other (`uri`, for example). Also makes `Transmogrifier.upgrade_user_from_ap_id` be called from `ActivityPub.make_user_from_ap_id` only when the user is actually not AP enabled yet. I did not bother rewriting tests that used `User.insert_or_update` to use the changeset instead because they seemed to just test the implementation, rather than behavior.
Diffstat (limited to 'test/web')
-rw-r--r--test/web/activity_pub/views/user_view_test.exs2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/web/activity_pub/views/user_view_test.exs b/test/web/activity_pub/views/user_view_test.exs
index ecb2dc386..514fd97b8 100644
--- a/test/web/activity_pub/views/user_view_test.exs
+++ b/test/web/activity_pub/views/user_view_test.exs
@@ -29,7 +29,7 @@ defmodule Pleroma.Web.ActivityPub.UserViewTest do
{:ok, user} =
insert(:user)
- |> User.upgrade_changeset(%{fields: fields})
+ |> User.update_changeset(%{fields: fields})
|> User.update_and_set_cache()
assert %{