protected_record_manager 0.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 753f89212104880cca2f99d0bb0b09ae301db1bd
+  data.tar.gz: 25c56476258179da950263d3f0caba04001f927b
+SHA512:
+  metadata.gz: 240bd9a848fb9cc3300ba78f61409ae342345b912a6a4cadd5d952a6281803452dd4c0d15d7d7314915d771a93f7da0087f39762f6e4531c96849aa1df71b625
+  data.tar.gz: ee8e9461970669bc72dc347a420ca16ea7aad178cbc647a6d7ffc8116951ff67c56ccfe07fe0922e3396d18ce41d17a70b98f2db3afd584167d5a25814c6c466

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2013 YOURNAME
+
+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.

data/README.rdoc

@@ -0,0 +1,3 @@
+= ProtectedRecordManager
+
+This project rocks and uses MIT-LICENSE.

data/Rakefile

@@ -0,0 +1,40 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'ProtectedRecordManager'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../test/dummy/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+
+
+Bundler::GemHelper.install_tasks
+
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = false
+end
+
+
+task :default => :test

data/app/assets/javascripts/protected_record_manager/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/app/assets/stylesheets/protected_record_manager/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+ */

data/app/controllers/protected_record_manager/application_controller.rb

@@ -0,0 +1,12 @@
+module ProtectedRecordManager
+  class ApplicationController < ActionController::Base
+    def ensure_record_manager
+      current_user || not_found
+      current_user.protected_record_manager || not_found
+    end
+
+    def not_found
+      render status: 403, text: 'Resource does not exist, or user lacks required permissions.' and return
+    end
+  end
+end

data/app/controllers/protected_record_manager/change_requests_controller.rb

@@ -0,0 +1,80 @@
+require_dependency "protected_record_manager/application_controller"
+
+module ProtectedRecordManager
+  class ChangeRequestsController < ApplicationController
+    before_filter :ensure_record_manager
+
+    # GET /change_requests
+    # GET /change_requests.json
+    def index
+      if current_user.protected_record_manager
+        @change_requests = ProtectedRecord::ChangeRequest::Record.where(closed_by_id: nil)
+      end
+
+      respond_to do |format|
+        format.html # index.html.erb
+        format.json { render json: @change_requests }
+      end
+    end
+
+    # GET /change_requests/1
+    # GET /change_requests/1.json
+    def show
+      @change_request = ProtectedRecord::ChangeRequest::Record.find(params[:id])
+
+      respond_to do |format|
+        format.html # show.html.erb
+        format.json { render json: @change_request }
+      end
+    end
+
+    # GET /change_requests/1/edit
+    def edit
+      @change_request = ProtectedRecord::ChangeRequest::Record.find(params[:id])
+    end
+
+    # PUT /change_requests/1
+    # PUT /change_requests/1.json
+    def update
+      @change_request = ProtectedRecord::ChangeRequest::Record.find(params[:id])
+
+      protected_record = @change_request.recordable
+      changes = ActiveSupport::JSON.decode(@change_request.requested_changes)
+
+      changes.each do |k,v|
+        changes[k] = v.last
+      end
+
+      ActiveRecord::Base.transaction do
+        # Save the request as closed
+        @change_request.closed_by_id = current_user.id
+        @change_request.save
+
+        # Make the change
+        binding.pry
+        ProtectedRecord::UseCase::Update.new({
+          params:           changes,
+          user:             current_user,
+          protected_record: protected_record,
+          protected_keys:   []
+        }).execute!
+
+        # Log the closing of this request
+        ProtectedRecord::UseCase::ChangeLog::Create.new({
+          record_class: ProtectedRecord::ChangeLog::Record,
+          user:         current_user,
+          changed_object: @change_request
+        }).execute!
+      end
+
+      respond_to do |format|
+        if @change_request.closed_by_id.present?
+          format.html { redirect_to change_request_path(@change_request), notice: 'Change request was successfully updated.' }
+        else
+          flash[:alert] = "Changes not applied."
+          format.html { render action: "edit" }
+        end
+      end
+    end
+  end
+end

data/app/helpers/protected_record_manager/application_helper.rb

@@ -0,0 +1,4 @@
+module ProtectedRecordManager
+  module ApplicationHelper
+  end
+end

data/app/helpers/protected_record_manager/change_requests_helper.rb

@@ -0,0 +1,4 @@
+module ProtectedRecordManager
+  module ChangeRequestsHelper
+  end
+end

data/app/views/layouts/protected_record_manager/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>ProtectedRecordManager</title>
+  <%= stylesheet_link_tag    "protected_record_manager/application", :media => "all" %>
+  <%= javascript_include_tag "protected_record_manager/application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>

data/app/views/protected_record_manager/change_requests/_form.html.erb

@@ -0,0 +1,35 @@
+<%= form_for(@change_request, method: "PUT", url: change_request_path(@change_request)) do |f| %>
+  <% if @change_request.errors.any? %>
+    <div id="error_explanation">
+      <h2><%= pluralize(@change_request.errors.count, "error") %> prohibited this change_request from being saved:</h2>
+
+      <ul>
+      <% @change_request.errors.full_messages.each do |msg| %>
+        <li><%= msg %></li>
+      <% end %>
+      </ul>
+    </div>
+
+
+  <% end %>
+
+  <strong>Apply changes and close request</strong>
+  <dl>
+
+  <dt> Record Type </dt>
+  <dd><%= @change_request.recordable_type %></dd>
+
+
+  <dt> Record ID </dt>
+  <dd><%= @change_request.recordable_id %></dd>
+
+
+  <dt> Changes </dt>
+  <dd><%= @change_request.requested_changes %></dd>
+
+  </dl>
+
+  <div class="actions">
+    <%= f.submit "Apply & Close" %>
+  </div>
+<% end %>

data/app/views/protected_record_manager/change_requests/edit.html.erb

@@ -0,0 +1,6 @@
+<h1>Editing change_request</h1>
+
+<%= render 'form' %>
+
+<%= link_to 'Show', change_request_path(@change_request) %> |
+<%= link_to 'Back', change_requests_path %>

data/app/views/protected_record_manager/change_requests/index.html.erb

@@ -0,0 +1,26 @@
+<h1>Listing Change Requests</h1>
+
+<table>
+  <tr>
+    <th>User</th>
+    <th>Record Type</th>
+    <th>Record ID</th>
+    <th>Changes</th>
+
+    <th></th>
+    <th></th>
+  </tr>
+
+<% @change_requests.each do |change_request| %>
+  <tr>
+    <td><%= change_request.user.email %></td>
+    <td><%= change_request.recordable_type %></td>
+    <td style="text-align:center;"><%= change_request.recordable_id %></td>
+    <td><%= change_request.requested_changes %></td>
+    <td><%= link_to 'Show', change_request_path(change_request) %></td>
+    <td><%= link_to 'Edit', edit_change_request_path(change_request) %></td>
+  </tr>
+<% end %>
+</table>
+
+<br />

data/app/views/protected_record_manager/change_requests/show.html.erb

@@ -0,0 +1,19 @@
+<p id="notice"><%= notice %></p>
+<dl>
+
+<dt> Record Type </dt>
+<dd><%= @change_request.recordable_type %></dd>
+
+
+<dt> Record ID </dt>
+<dd><%= @change_request.recordable_id %></dd>
+
+
+<dt> Changes </dt>
+<dd><%= @change_request.requested_changes %></dd>
+
+</dl>
+
+
+<%= link_to 'Edit', edit_change_request_path(@change_request) %> |
+<%= link_to 'Back', change_requests_path %>

data/config/routes.rb

@@ -0,0 +1,4 @@
+ProtectedRecordManager::Engine.routes.draw do
+  resources :change_requests, controller: "change_requests",
+    except: [:destroy, :new, :create]
+end

data/db/migrate/20130424181224_add_protected_record_manager_to_users.rb

@@ -0,0 +1,5 @@
+class AddProtectedRecordManagerToUsers < ActiveRecord::Migration
+  def change
+    add_column :users, :protected_record_manager, :boolean
+  end
+end

data/db/migrate/20130424195950_create_protected_record_change_log_records.rb

@@ -0,0 +1,12 @@
+class CreateProtectedRecordChangeLogRecords < ActiveRecord::Migration
+  def change
+    create_table :protected_record_change_log_records do |t|
+      t.integer :user_id
+      t.integer :recordable_id
+      t.string  :recordable_type
+      t.string  :observed_changes
+
+      t.timestamps
+    end
+  end
+end

data/db/migrate/20130424195959_create_protected_record_change_request_records.rb

@@ -0,0 +1,13 @@
+class CreateProtectedRecordChangeRequestRecords < ActiveRecord::Migration
+  def change
+    create_table :protected_record_change_request_records do |t|
+      t.integer :user_id
+      t.integer :recordable_id
+      t.string  :recordable_type
+      t.text    :requested_changes
+      t.integer :closed_by_id
+
+      t.timestamps
+    end
+  end
+end

data/lib/protected_record_manager/engine.rb

@@ -0,0 +1,5 @@
+module ProtectedRecordManager
+  class Engine < ::Rails::Engine
+    isolate_namespace ProtectedRecordManager
+  end
+end

data/lib/protected_record_manager/version.rb

@@ -0,0 +1,3 @@
+module ProtectedRecordManager
+  VERSION = "0.0.0"
+end

data/lib/protected_record_manager.rb

@@ -0,0 +1,4 @@
+require "protected_record_manager/engine"
+
+module ProtectedRecordManager
+end

data/lib/tasks/protected_record_manager_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :protected_record_manager do
+#   # Task goes here
+# 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
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- 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.