trust 0.5.0

data/lib/trust/permissions.rb

@@ -0,0 +1,268 @@
+# Copyright (c) 2012 Bingo Entreprenøren AS
+# Copyright (c) 2012 Teknobingo Scandinavia AS
+# Copyright (c) 2012 Knut I. Stenmark
+# Copyright (c) 2012 Patrick Hanevold
+#
+# Permission is hereby granted, free of charge, to any person obtaining
+# a copy of this software and associated documentation files (the
+# "Software"), to deal in the Software without restriction, including
+# without limitation the rights to use, copy, modify, merge, publish,
+# distribute, sublicense, and/or sell copies of the Software, and to
+# permit persons to whom the Software is furnished to do so, subject to
+# the following conditions:
+#
+# The above copyright notice and this permission notice shall be
+# included in all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+# LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+# WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+module Trust
+  class Permissions
+    # = Trust::Permissions
+    # Permissions should be specified in a separate file in you app/model directory. The file could look like this:
+    #
+    #   module Permissions
+    #     class Default < Trust::Permissions
+    #       ...
+    #     end
+    #     ...
+    #   end
+    #
+    # The above is the minimum required definitions that must exist in you file. <tt>Default</tt> will be used if no classes
+    # match the permissions requested, so the <tt>Default</tt> class definition is mandatory.
+    #
+    # If you want to separate the permissions into separate files that is ok. Then you shoud place these files in the 
+    # /app/model/permissions directory.
+    #
+    # === Defining permisions
+    #
+    # The basic rules is to define classes in the Permissions module that matches your models.
+    # Here are some examples:
+    # * <tt>Project</tt> should have a matching class <tt>Permissions::Project</tt>
+    # * <tt>Account</tt> should have a matching class <tt>Permissions::Account</tt>
+    # * <tt>Account:Credit</tt> may have a matching class <tt>Permissions::Account::Credit</tt>, but if its inheriting from
+    #   <tt>Account</tt> and no special handling is necessary, it is not necessary to create the permissions class.
+    #
+    # === Using inheritance
+    #
+    # Inheritance is also fully supported, but should generally follow your own inheritance model
+    # 
+    #   module Permissions
+    #     class Account < Default
+    #       role :admin, :accountant do 
+    #         ...
+    #       end
+    #     end
+    #     class Account::Credit < Account
+    #       ...
+    #     end
+    #   end
+    #
+    # === Action aliases
+    #
+    # You can define aliases for actions. You do this by setting the <tt>action_aliases</tt> attribute on Trust::Permissions class
+    # Example:
+    #   Trust::Permissions.action_aliases = {
+    #      read: [:index, :show],
+    #      create: [:create, :new]
+    #      }
+    #
+    # Keep in mind that all permissions are expanded upon declaration, so when using the <tt>can?</tt> method you must refer to 
+    # the actual action and not the alias. The alias will never give a positive permission.
+    #
+    # === Accessors
+    #
+    # Accessors that can be used when testing permissions:
+    # * <tt>user</tt> - the user currently logged in
+    # * <tt>action</tt> - the action request from the controller such as :edit, or the action tested from helper or 
+    #   from the object itself when using <tt>ActiveRecord::can?</tt> is being used.
+    # * <tt>subject</tt> - the object that is being tested for permissions. This may be a an existing object, a new object
+    #   (such as for +:create+ and +:new+ action), or nil if no object has been instantiated.
+    # * <tt>parent</tt> - the parent object if in a nested route, specified by +belongs_to+ in the controller.
+    # * <tt>klass</tt> - the class of involed in the request. It can be a base class or the real class, depending on
+    #   your controller design.
+    #
+    # === Defining your own accessors or instance methods
+    #
+    # You can easily define your own accessors in the classes. These can be helpful when declaring permissions.
+    # Example:
+    #
+    #   class Account < Trust::Permissions
+    #     role :admin, :accountant do
+    #       can :update, :unless => :closed?
+    #     end
+    #     def closed? 
+    #       subject.closed?
+    #     end
+    #   end
+    #
+    # In the above example closed is testing on the subject to see if it is closed. The permission is referring to 
+    # this method when evaluated.
+    # Keep in mind that you must refer to the +subject+, as you do not access the inctance of the object directly.
+    #
+    
+    
+    include InheritableAttribute
+    attr_reader :user, :action, :klass, :subject, :parent
+    inheritable_attr :permissions
+    class_attribute :action_aliases, :instance_writer => false, :instance_reader => false
+    self.permissions = {}
+    self.action_aliases = {
+      read: [:index, :show],
+      create: [:create, :new],
+      update: [:update, :edit],
+      manage: [:index, :show, :create, :new, :update, :edit, :destroy]
+      }
+    @@can_expressions = 0
+  
+    # initializes the permission object
+    # calling the +authorized?+ method on the instance later will test for the authorization.
+    # Parameters:
+    # <tt>user</tt> - user object, must respond to role_symbols
+    # <tt>action</tt> - action, such as :create, :show, etc. Should not be an alias
+    # <tt>klass</tt> - the class of the subject. 
+    # <tt>subject</tt> - the subject tested for authorization
+    # <tt>parent</tt> - the parent object, normally declared through belongs_to
+    #
+    # See Trust::Authorization for more details
+    def initialize(user, action, klass, subject, parent)
+      @user, @action, @klass, @subject, @parent = user, action, klass, subject, parent
+    end
+  
+    # returns true if the user is authorized to perform the action
+    def authorized?
+      authorized = nil
+      user && user.role_symbols.each do |role|
+        (permissions[role] || {}).each do |act, opt|
+          if act == action
+            break if (authorized = opt.any? ? eval_expr(opt) : true)
+          end
+        end
+        break if authorized
+      end
+      authorized
+    end
+  
+  protected
+    def eval_expr(options) #:nodoc:
+      options.collect do |oper, expr|
+        res = case expr
+        when Symbol then send(expr)
+        when Proc
+          if expr.lambda?
+            instance_exec &expr
+          else
+            instance_eval &expr
+          end
+        else
+          expr
+        end
+
+        case oper
+        when :if then res
+        when :unless then !res
+        else
+          raise UnsupportedCondition, expr.inspect
+        end
+      end.all?
+    end
+  
+    class << self
+      # Assign permissions to one or more roles.
+      # You may call role or roles, they are the same function like <tt>role :admin</tt> or <tt>roles :admin, :accountant</tt>
+      #
+      # There are two ways to call role, with or without block. If you want to set multiple permissions with different conditons
+      # then you should use a block.
+      #
+      #   module Permissions
+      #     class Account < Trust::Permissions
+      #       role :admin, can(:manage, :audit)
+      #     end
+      #   end
+      #
+      # The above assigns the manage and audit permissions to admin.
+      #
+      #   module Permissions
+      #     class Account < Trust::Permissions
+      #       role :admin, :accountant do 
+      #         can :read
+      #         can :update
+      #       end
+      #     end
+      #   end
+      # 
+      # The above permits admin and accountant to read accounts.
+      def role(*roles, &block)
+        if block_given?
+          if @@can_expressions > 0
+            @@can_expressions = 0
+            raise RoleAssigmnentMissing 
+          end
+          @perms = []
+          @in_role_block = true
+          yield
+          @in_role_block = false
+          perms = @perms          
+        else
+          if @@can_expressions > 1
+            @@can_expressions = 0
+            raise RoleAssigmnentMissing 
+          end
+          options = roles.extract_options!
+          raise ArgumentError, "Must have a block or a can expression" unless perms = options[:can]
+          @@can_expressions = 0
+        end
+        roles.flatten.each do |role|
+          self.permissions[role] ||= []
+          self.permissions[role] += perms
+        end
+      end
+      alias :roles :role
+  
+      # Defines permissions
+      #   action - can be an alias or an actions of some kind
+      #   options - :if/:unless :symbol or proc that will be called to evaluate an expression
+      #
+      #   module Permissions
+      #     class Account < Trust::Permissions
+      #       role :admin, :accountant do 
+      #         can :read
+      #         can :update, :unless => :closed?
+      #       end
+      #     end
+      #   end
+      # 
+      # The above permits admin and accountant to read accounts, but can update only if the account is not closed.
+      # In the example above a method is used to test data on the actual record when testing for permissions.
+      def can(*args)
+        options = args.extract_options!
+        p = expand_aliases(args).collect { |action| [action, options] }
+        if @in_role_block
+          @perms += p
+        else
+          @@can_expressions += 1
+          return {:can => p }
+        end
+      end
+  
+    private
+      def expand_aliases(actions) #:nodoc:
+        expanded = []
+        Array.wrap(actions).each do |action|
+          if self.action_aliases[action]
+            expanded += Array.wrap(self.action_aliases[action])
+          else
+            expanded << action
+          end
+        end
+        expanded
+      end
+    end
+  end
+end

data/lib/trust/test_helper.rb

@@ -0,0 +1,56 @@
+# Copyright (c) 2012 Bingo Entreprenøren AS
+# Copyright (c) 2012 Teknobingo Scandinavia AS
+# Copyright (c) 2012 Knut I. Stenmark
+# Copyright (c) 2012 Patrick Hanevold
+#
+# Permission is hereby granted, free of charge, to any person obtaining
+# a copy of this software and associated documentation files (the
+# "Software"), to deal in the Software without restriction, including
+# without limitation the rights to use, copy, modify, merge, publish,
+# distribute, sublicense, and/or sell copies of the Software, and to
+# permit persons to whom the Software is furnished to do so, subject to
+# the following conditions:
+#
+# The above copyright notice and this permission notice shall be
+# included in all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+# LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+# WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+class Trust::ResourceHelper
+  attr_accessor :instance, :parent, :instances
+  attr_accessor :properties, :params, :action, :instance_params
+  attr_accessor :info, :parent_info, :relation
+  class << self
+    attr_accessor :properties
+  end
+  
+  def klass
+    instance.class
+  end
+  
+  def instance_name
+    Trust::Controller::Resource::Info.var_name(klass)
+  end
+  
+  def parent_name
+    Trust::Controller::Resource::Info.var_name(parent.class)
+  end
+  
+  def instantiated
+    instances || instance
+  end
+end
+
+class ActionView::TestCase
+  # allows you to stub resource for helpers
+  def resource
+    @resource ||= Trust::ResourceHelper.new    
+  end
+end
+

data/lib/trust/version.rb

@@ -0,0 +1,27 @@
+# Copyright (c) 2012 Bingo Entreprenøren AS
+# Copyright (c) 2012 Teknobingo Scandinavia AS
+# Copyright (c) 2012 Knut I. Stenmark
+# Copyright (c) 2012 Patrick Hanevold
+#
+# Permission is hereby granted, free of charge, to any person obtaining
+# a copy of this software and associated documentation files (the
+# "Software"), to deal in the Software without restriction, including
+# without limitation the rights to use, copy, modify, merge, publish,
+# distribute, sublicense, and/or sell copies of the Software, and to
+# permit persons to whom the Software is furnished to do so, subject to
+# the following conditions:
+#
+# The above copyright notice and this permission notice shall be
+# included in all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+# LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+# WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+module Trust
+  VERSION = "0.5.0"
+end

data/lib/trust.rb

@@ -0,0 +1,39 @@
+# Copyright (c) 2012 Bingo Entreprenøren AS
+# Copyright (c) 2012 Teknobingo Scandinavia AS
+# Copyright (c) 2012 Knut I. Stenmark
+# Copyright (c) 2012 Patrick Hanevold
+#
+# Permission is hereby granted, free of charge, to any person obtaining
+# a copy of this software and associated documentation files (the
+# "Software"), to deal in the Software without restriction, including
+# without limitation the rights to use, copy, modify, merge, publish,
+# distribute, sublicense, and/or sell copies of the Software, and to
+# permit persons to whom the Software is furnished to do so, subject to
+# the following conditions:
+#
+# The above copyright notice and this permission notice shall be
+# included in all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+# LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+# WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+require 'trust/exceptions'
+require 'trust/inheritable_attribute'
+module Trust
+  autoload :Permissions,        'trust/permissions'
+  autoload :Controller,         'trust/controller'
+  autoload :Authorization,      'trust/authorization'
+  autoload :ActiveRecord,       'trust/active_record'
+end
+require 'trust/controller'
+class ActionController::Base
+  include Trust::Controller
+end
+class ActiveRecord::Base
+  include Trust::ActiveRecord
+end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.

data/test/dummy/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+Dummy::Application.load_tasks

data/test/dummy/app/assets/javascripts/accounts.js

@@ -0,0 +1,2 @@
+// Place all the behaviors and hooks related to the matching controller here.
+// All this logic will automatically be available in application.js.

data/test/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/test/dummy/app/assets/javascripts/clients.js

@@ -0,0 +1,2 @@
+// Place all the behaviors and hooks related to the matching controller here.
+// All this logic will automatically be available in application.js.

data/test/dummy/app/assets/javascripts/users.js

@@ -0,0 +1,2 @@
+// Place all the behaviors and hooks related to the matching controller here.
+// All this logic will automatically be available in application.js.