Ask the user about their current user when generating a config file

Author: benmcredmond

lib/rails/generators/intercom/config/config_generator.rb

@@ -10,11 +10,34 @@ def self.source_root
       argument :api_secret, :desc => "Your Intercom api-secret, used for secure mode", :optional => true
       argument :api_key, :desc => "An Intercom API key, for various rake tasks", :optional => true
 
+      FALSEY_RESPONSES = ['n', 'no']
       def create_config_file
         @app_id = app_id
         @api_secret = api_secret
         @api_key = api_key
 
+        introduction = <<-desc
+Intercom will automatically insert its javascript before the closing '</body>' 
+tag on every page where it can find a logged-in user. Intercom by default
+looks for logged-in users, in the controller, via 'current_user' and '@user'.
+
+Is the logged-in user accessible via either 'current_user' or '@user'? [Yn]
+        desc
+
+        print "#{introduction.strip} "
+        default_ok = $stdin.gets.strip.downcase 
+
+        if FALSEY_RESPONSES.include?(default_ok) 
+          custom_current_user_question = <<-desc
+
+How do you access the logged-in user in your controllers? This can be
+any Ruby code, e.g. 'current_customer', '@admin', etc.:
+          desc
+
+          print "#{custom_current_user_question.rstrip} "
+          @current_user = $stdin.gets.strip
+        end
+
         template("intercom.rb.erb", "config/initializers/intercom.rb")
       end
 

lib/rails/generators/intercom/config/intercom.rb.erb

@@ -27,7 +27,11 @@ IntercomRails.config do |config|
   # The method/variable that contains the logged in user in your controllers.
   # If it is `current_user` or `@user`, then you can ignore this
   #
+  <%- if @current_user -%>
+  config.user.current = Proc.new { <%= @current_user %> }
+  <%- else -%>
   # config.user.current = Proc.new { current_user }
+  <%- end -%>
 
   # == User model class
   # The class which defines your user model