nostalgia 0.0.1

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,11 @@
+source 'https://rubygems.org'
+
+gem 'activerecord', '>= 3.0.0'
+
+group :development, :test do
+  gem "shoulda", ">= 0"
+  gem 'sqlite3-ruby' 
+end
+
+# Specify your gem's dependencies in nostalgia.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Aaron Scruggs
+
+MIT License
+
+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,37 @@
+# Nostalgia
+
+Often I want to evaluate what changed on an object after it has saved and has been transactionally committed.  One use case is enqueuenig a background job when a specific attribute changed.  Typically you should wait until after_commit to enqueue the job.  This ensures that your workers will have access to the updates that were being made inside the transaction. This is a problem because ActiveRecord forgets the changes after_save.  This gem keeps those changes around for later inspection and evaluation.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'nostalgia'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install nostalgia
+
+## Usage
+
+    class Model < ActiveRecord::Base
+      include Nostalgia
+    end
+
+    model = Model.create(:foo => :bar)
+    model.nostalgia
+
+    #=> {:foo => [nil,:bar], :id => [nil, 1]}
+
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1,15 @@
+require "bundler/gem_tasks"
+
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'lib/test/**/*_test.rb'
+  t.verbose = false
+end
+
+task :default => :test
+
+
+

data/lib/nostalgia.rb

@@ -0,0 +1,20 @@
+require 'active_record'
+require "nostalgia/version"
+
+module Nostalgia
+  
+  def self.included(base)
+    base.send :after_save, :remember_nostalgia_changes
+  end
+
+  def nostalgia
+    @nostalgia || changes
+  end
+
+  private
+
+  def remember_nostalgia_changes
+    @nostalgia = changes.dup
+  end
+
+end

data/lib/nostalgia/version.rb

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

data/nostalgia.gemspec

@@ -0,0 +1,23 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'nostalgia/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "nostalgia"
+  spec.version       = Nostalgia::VERSION
+  spec.authors       = ["Aaron Scruggs"]
+  spec.email         = ["aaron@scrug.gs"]
+  spec.description   = %q{Often I want to evaluate what changed on an object after it has saved and has been transactionally committed.  One use case is enqueuenig a background job when a specific attribute changed.  Typically you should wait until after_commit to enqueue the job.  This ensures that your workers will have access to the updates that were being made inside the transaction. This is a problem because ActiveRecord forgets the changes after_save.  This gem keeps those changes around for later inspection and evaluation.}
+  spec.summary       = %q{Remember changes on ActiveRecord models even after they are saved.}
+  spec.homepage      = "http://github.com/AcademicWorks/nostalgia"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files`.split($/)
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.3"
+  spec.add_development_dependency "rake"
+end

metadata

@@ -0,0 +1,92 @@
+--- !ruby/object:Gem::Specification
+name: nostalgia
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+  prerelease: 
+platform: ruby
+authors:
+- Aaron Scruggs
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2013-04-28 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.3'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.3'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+description: Often I want to evaluate what changed on an object after it has saved
+  and has been transactionally committed.  One use case is enqueuenig a background
+  job when a specific attribute changed.  Typically you should wait until after_commit
+  to enqueue the job.  This ensures that your workers will have access to the updates
+  that were being made inside the transaction. This is a problem because ActiveRecord
+  forgets the changes after_save.  This gem keeps those changes around for later inspection
+  and evaluation.
+email:
+- aaron@scrug.gs
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- .gitignore
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- lib/nostalgia.rb
+- lib/nostalgia/version.rb
+- nostalgia.gemspec
+homepage: http://github.com/AcademicWorks/nostalgia
+licenses:
+- MIT
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.8.25
+signing_key: 
+specification_version: 3
+summary: Remember changes on ActiveRecord models even after they are saved.
+test_files: []