summaryrefslogtreecommitdiff
path: root/users/app/controllers
diff options
context:
space:
mode:
authorAzul <azul@leap.se>2013-08-30 11:20:04 +0200
committerAzul <azul@leap.se>2013-09-03 08:54:25 +0200
commit859b79d0dcd53c85bb57e3db888a1af702802987 (patch)
treecb0e293a6eddba2a9aa0b22baa0bfb43f56c43ed /users/app/controllers
parent0d44e39d2ec591c9ab98464b93a0c867ca96e02a (diff)
Account: Composition to handle User and its identities
We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests).
Diffstat (limited to 'users/app/controllers')
-rw-r--r--users/app/controllers/v1/users_controller.rb11
1 files changed, 4 insertions, 7 deletions
diff --git a/users/app/controllers/v1/users_controller.rb b/users/app/controllers/v1/users_controller.rb
index f380c19..b271152 100644
--- a/users/app/controllers/v1/users_controller.rb
+++ b/users/app/controllers/v1/users_controller.rb
@@ -18,23 +18,20 @@ module V1
end
def create
- @user = signup_service.register(params[:user])
+ @user = Account.create(params[:user])
respond_with @user # return ID instead?
end
def update
- account_settings.update params[:user]
+ account.update params[:user]
respond_with @user
end
protected
- def account_settings
- AccountSettings.new(@user)
+ def account
+ Account.new(@user)
end
- def signup_service
- SignupService.new
- end
end
end