sigame 0.0.1

data/MIT-LICENSE

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

@@ -0,0 +1,41 @@
+
+##sigame
+This gem allows you to add a way to your users to follow each other.
+
+##Getting started
+sigame works with Rails 3.2 onwards. You can add it to your Gemfile with:
+
+```ruby
+gem 'sigame'
+```
+
+Run the install generator to add an initializer file and copy a migration file:
+
+```
+rails g sigame:install
+```
+
+Migrate them:
+
+```
+rake db:migrate
+```
+
+It is heavily recommended for you to change railsties order in
+`config/application.rb`:
+
+```ruby
+config.railties_order = [Sigame::Engine, :main_app, :all]
+```
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+## License
+This project is released under the [MIT
+License](http://www.opensource.org/licenses/MIT)

data/Rakefile

@@ -0,0 +1,29 @@
+#!/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    = 'Sigame'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../spec/dummy/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+
+
+Bundler::GemHelper.install_tasks
+

data/app/controllers/followings_controller.rb

@@ -0,0 +1,17 @@
+# -*- encoding : utf-8 -*-
+class FollowingsController < ApplicationController
+  before_filter :authenticate!
+  def create
+    @following = current_user.followings.create(followed: followed)
+    redirect_to followed, notice: "Agora você está observando #{followed.name}!"
+  end
+  def destroy
+    @following = current_user.followings.find_by_followed_id!(followed.id)
+    @following.destroy
+    redirect_to followed, notice: "Você deixou de observar #{followed.name}!"
+  end
+  private
+  def followed
+    @followed ||= User.find(params[:user_id])
+  end
+end

data/app/models/following.rb

@@ -0,0 +1,22 @@
+# -*- encoding : utf-8 -*-
+class Following < ActiveRecord::Base
+  belongs_to :user
+  belongs_to :followed, class_name: "User"
+  validates :user, :followed, presence: true
+  validates :followed_id, uniqueness: { scope: :user_id }
+  validate :validate_following_himself?
+  attr_accessible :followed
+  after_create :increment_followed_followers
+  after_destroy :decrement_followed_followers
+  private
+    def validate_following_himself?
+      return unless user && followed
+      errors.add(:followed, "não pode ser o próprio") if user.eql?(followed)
+    end
+    def increment_followed_followers
+      followed.increment!(:followers_count)
+    end
+    def decrement_followed_followers
+      followed.decrement!(:followers_count)
+    end
+end

data/config/routes.rb

@@ -0,0 +1,5 @@
+Rails.application.routes.draw do
+  resources :users, only: [:show] do
+    resource :followings, only: [:create, :destroy]
+  end
+end

data/db/migrate/20120808132126_create_followings.rb

@@ -0,0 +1,13 @@
+class CreateFollowings < ActiveRecord::Migration
+  def change
+    create_table :followings do |t|
+      t.references :user
+      t.references :followed
+
+      t.timestamps
+    end
+    add_index :followings, :user_id
+    add_index :followings, :followed_id
+    add_index :followings, [:user_id, :followed_id], :unique => true
+  end
+end

data/lib/generators/sigame/install/USAGE

@@ -0,0 +1,8 @@
+Description:
+    Copies migrations
+
+Example:
+    rails generate sigame:install
+
+    This will create:
+        db/migrate/xxxx_xxxx_create_followings.rb

data/lib/generators/sigame/install/install_generator.rb

@@ -0,0 +1,8 @@
+module Sigame
+  class InstallGenerator < Rails::Generators::Base
+    source_root File.expand_path('../templates', __FILE__)
+    def copy_migrations
+      rake("sigame_engine:install:migrations")
+    end
+  end
+end

data/lib/sigame.rb

@@ -0,0 +1,9 @@
+require "sigame/engine"
+if Rails.env.to_s == "test"
+  require 'shoulda-matchers'
+  require 'factory_girl'
+  require File.expand_path('../../spec/factories', __FILE__)
+end
+
+module Sigame
+end

data/lib/sigame/engine.rb

@@ -0,0 +1,15 @@
+module Sigame
+  class Engine < ::Rails::Engine
+    config.generators do |g|
+      g.test_framework :rspec, :view_specs => false
+    end
+    initializer "sigame.raise_if_required_methods_not_defined" do |app|
+      dummy_controller = FollowingsController.new
+      unless dummy_controller.respond_to?(:authenticate!) && dummy_controller.respond_to?(:current_user)
+        raise "You don't have authenticate! and current_user methods defined in your ApplicationController, and sigame requires both of them."
+      end
+      #Raise error if User is not defined
+      Module.const_get("User")
+    end
+  end
+end

data/lib/sigame/version.rb

@@ -0,0 +1,3 @@
+module Sigame
+  VERSION = "0.0.1"
+end

data/lib/tasks/sigame_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :sigame do
+#   # Task goes here
+# end

data/spec/controllers/followings_controller_spec.rb

@@ -0,0 +1,72 @@
+# -*- encoding : utf-8 -*-
+require 'spec_helper'
+CURRENT_USER = FactoryGirl.create :user
+FollowingsController.class_eval do
+  def current_user
+    CURRENT_USER
+  end
+end
+def current_user
+  CURRENT_USER
+end
+
+describe FollowingsController do
+  describe :create do
+    let(:followed) { FactoryGirl.create(:user, name: "Cajuina da Silva") }
+    def do_action
+      post :create, user_id: followed.id.to_s
+    end
+    context :logged_in do
+      context :regular do
+        before { do_action }
+        it { should assign_to(:followed).with(followed) }
+        it { should set_the_flash.to('Agora você está observando Cajuina da Silva!') }
+        it { should redirect_to(followed) }
+      end
+      context :complex do
+        it {
+          expect {
+            do_action
+          }.to change { Following.count }.by(1)
+        }
+      end
+      context :following do
+        before { do_action }
+        subject { assigns(:following) }
+        its(:user) { should == current_user }
+        its(:followed) { should == followed }
+      end
+    end
+  end
+  describe :destroy do
+    let(:followed) { FactoryGirl.create(:user, name: "Cajuina da Silva") }
+    let!(:following) { FactoryGirl.create(:following, user: current_user, followed: followed) }
+    def do_action
+      delete :destroy, user_id: followed.id.to_s
+    end
+    context :logged_in do
+      context :regular do
+        before { do_action }
+        it { should assign_to(:followed).with(followed) }
+        it { should set_the_flash.to('Você deixou de observar Cajuina da Silva!') }
+        it { should redirect_to(followed) }
+      end
+      context :complex do
+        it {
+          expect {
+            do_action
+          }.to change { Following.count }.by(-1)
+        }
+      end
+      context :following do
+        before { do_action }
+        subject { assigns(:following) }
+        it {
+          expect {
+            following.reload
+          }.to raise_error(ActiveRecord::RecordNotFound)
+        }
+      end
+    end
+  end
+end

data/spec/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.