fix linting errors

app/controllers/api/v1/surf/emails_controller.rb

@@ -7,7 +7,7 @@ class Api::V1::Surf::EmailsController < Api::BaseController
   before_action :current_user
 
   def confirmation
-    confirmation_params = {:confirmation_token => @current_user.confirmation_token}
+    confirmation_params = { :confirmation_token => @current_user.confirmation_token }
     confirmation_url = "/auth/confirmation?#{confirmation_params.to_query}"
     render json: {
       base_url: request.base_url,

app/controllers/api/v1/surf/users_controller.rb

@@ -16,11 +16,12 @@ def whoami
   # unconfirmed user access and might need to
   # get the confirmation_token for sending the email
   protected
+
   def require_user!
-    if !current_user
-      render json: { error: 'This method requires an authenticated user' }, status: 422
-    else
+    if current_user
       update_user_sign_in
+    else
+      render json: { error: 'This method requires an authenticated user' }, status: 422
     end
   end
 end

app/services/surf_app_sign_up_service.rb

@@ -32,4 +32,4 @@ def create_user!
     @user.skip_confirmation_notification!
     @user.save!
   end
-end
+end

dev/README.md

@@ -6,9 +6,11 @@
 # Running Apps
 
 From the root of the repo run this the first time:
+
 - `docker-compose -f dev/docker-compose.yml up --build`
 
 Or, if restarting:
+
 - `docker-compose -f dev/docker-compose.yml up`
 
 The app takes a while to start. Patience, my friend.
@@ -42,6 +44,7 @@ The developer setup doesn't configure SSL and uses nginx as a reverse proxy (see
 - `docker-compose -f dev/docker-compose.yml down`
 
 This is helpful if we're making changes to how the docker-compose stuff runs and we want to start fresh:
+
 - `./dev/clean.sh`
 
 # OAuth Client Testing
@@ -57,4 +60,4 @@ Once you cache the client and or users...
 
 ```
 ./dev/debug/emails.sh
-```
+```