lockbox_middleware 1.2.1 → 1.2.2

data/vendor/gems/factory_girl-1.2.3/README.rdoc

@@ -1,228 +0,0 @@
-= factory_girl
-
-factory_girl is a fixtures replacement with a straightforward definition syntax, support for multiple build strategies (saved instances, unsaved instances, attribute hashes, and stubbed objects), and support for multiple factories for the same class (user, admin_user, and so on), including factory inheritance.
-
-== Download
-
-Github: http://github.com/thoughtbot/factory_girl/tree/master
-
-Gem:
-  gem install thoughtbot-factory_girl --source http://gems.github.com
-
-Note: if you install factory_girl using the gem from Github, you'll need this
-in your environment.rb if you want to use Rails 2.1+'s dependency manager:
-
-  config.gem "thoughtbot-factory_girl",
-             :lib    => "factory_girl",
-             :source => "http://gems.github.com"
-
-== Defining factories
-
-Each factory has a name and a set of attributes. The name is used to guess the class of the object by default, but it's possible to explicitly specify it:
-
-  # This will guess the User class
-  Factory.define :user do |u|
-    u.first_name 'John'
-    u.last_name  'Doe'
-    u.admin false
-  end
-
-  # This will use the User class (Admin would have been guessed)
-  Factory.define :admin, :class => User do |u|
-    u.first_name 'Admin'
-    u.last_name  'User'
-    u.admin true
-  end
-
-  # The same, but using a string instead of class constant
-  Factory.define :admin, :class => 'user' do |u|
-    u.first_name 'Admin'
-    u.last_name  'User'
-    u.admin true
-  end
-
-It is highly recommended that you have one factory for each class that provides the simplest set of attributes necessary to create an instance of that class. If you're creating ActiveRecord objects, that means that you should only provide attributes that are required through validations and that do not have defaults. Other factories can be created through inheritance to cover common scenarios for each class.
-
-Factories can either be defined anywhere, but will automatically be loaded if they are defined in files at the following locations:
-
-  test/factories.rb
-  spec/factories.rb
-  test/factories/*.rb
-  spec/factories/*.rb
-
-== Using factories
-
-factory_girl supports several different build strategies: build, create, attributes_for and stub:
-
-  # Returns a User instance that's not saved
-  user = Factory.build(:user)
-
-  # Returns a saved User instance
-  user = Factory.create(:user)
-
-  # Returns a hash of attributes that can be used to build a User instance:
-  attrs = Factory.attributes_for(:user)
-
-  # Returns an object with all defined attributes stubbed out:
-  stub = Factory.stub(:user)
-
-You can use the Factory method as a shortcut for the default build strategy:
-
-  # Same as Factory.create :user:
-  user = Factory(:user)
-
-The default strategy can be overriden:
-
-  # Now same as Factory.build(:user)
-  Factory.define :user, :default_strategy => :build do |u|
-    ...
-  end
-
-  user = Factory(:user)
-
-No matter which startegy is used, it's possible to override the defined attributes by passing a hash:
-
-  # Build a User instance and override the first_name property
-  user = Factory.build(:user, :first_name => 'Joe')
-  user.first_name
-  # => "Joe"
-
-== Lazy Attributes
-
-Most factory attributes can be added using static values that are evaluated when the factory is defined, but some attributes (such as associations and other attributes that must be dynamically generated) will need values assigned each time an instance is generated. These "lazy" attributes can be added by passing a block instead of a parameter:
-
-  Factory.define :user do |u|
-    # ...
-    u.activation_code { User.generate_activation_code }
-  end
-
-== Dependent Attributes
-
-Attributes can be based on the values of other attributes using the proxy that is yieled to lazy attribute blocks:
-
-  Factory.define :user do |u|
-    u.first_name 'Joe'
-    u.last_name  'Blow'
-    u.email {|a| "#{a.first_name}.#{a.last_name}@example.com".downcase }
-  end
-
-  Factory(:user, :last_name => 'Doe').email
-  # => "joe.doe@example.com"
-
-== Associations
-
-Associated instances can be generated by using the association method when
-defining a lazy attribute:
-
-  Factory.define :post do |p|
-    # ...
-    p.author {|author| author.association(:user, :last_name => 'Writely') }
-  end
-
-The behavior of the association method varies depending on the build strategy used for the parent object.
-
-  # Builds and saves a User and a Post
-  post = Factory(:post)
-  post.new_record?       # => false
-  post.author.new_record # => false
-
-  # Builds and saves a User, and then builds but does not save a Post
-  Factory.build(:post)
-  post.new_record?       # => true
-  post.author.new_record # => false
-
-Because this pattern is so common, a prettier syntax is available for defining
-associations:
-
-  # The following definitions are equivilent:
-  Factory.define :post do |p|
-    p.author {|a| a.association(:user) }
-  end
-
-  Factory.define :post do |p|
-    p.association :author, :factory => :user
-  end
-
-If the factory name is the same as the association name, the factory name can
-be left out.
-
-== Inheritance
-
-You can easily create multiple factories for the same class without repeating common attributes by using inheritance:
-
-  Factory.define :post do |p|
-    # the 'title' attribute is required for all posts
-    p.title 'A title'
-  end
-
-  Factory.define :approved_post, :parent => :post do |p|
-    p.approved true
-    # the 'approver' association is required for an approved post
-    p.association :approver, :factory => :user
-  end
-
-== Sequences
-
-Unique values in a specific format (for example, e-mail addresses) can be
-generated using sequences. Sequences are defined by calling Factory.sequence,
-and values in a sequence are generated by calling Factory.next:
-
-  # Defines a new sequence
-  Factory.sequence :email do |n|
-    "person#{n}@example.com"
-  end
-
-  Factory.next :email
-  # => "person1@example.com"
-
-  Factory.next :email
-  # => "person2@example.com"
-
-Sequences can be used in lazy attributes:
-
-  Factory.define :user do |f|
-    f.email { Factory.next(:email) }
-  end
-
-And it's also possible to define an in-line sequence that is only used in
-a particular factory:
-
-  Factory.define :user do |f|
-    f.sequence(:email) {|n| "person#{n}@example.com" }
-  end
-
-== Alternate Syntaxes
-
-Users' tastes for syntax vary dramatically, but most users are looking for a common feature set. Because of this, factory_girl supports "syntax layers" which provide alternate interfaces. See Factory::Syntax for information about the various layers available.
-
-== More Information
-
-Our blog: http://giantrobots.thoughtbot.com
-
-factory_girl rdoc: http://rdoc.info/projects/thoughtbot/factory_girl
-
-Mailing list: http://groups.google.com/group/factory_girl
-
-factory_girl issues: http://github.com/thoughtbot/factory_girl/issues
-
-== Contributing
-
-Please read the contribution guidelines before submitting patches or pull requests.
-
-== Author
-
-factory_girl was written by Joe Ferris with contributions from several authors, including:
-* Alex Sharp
-* Eugene Bolshakov
-* Jon Yurek
-* Josh Nichols
-* Josh Owens
-
-The syntax layers are derived from software written by the following authors:
-* Pete Yandell
-* Rick Bradley
-* Yossef Mendelssohn
-
-Thanks to all members of thoughtbot for inspiration, ideas, and funding.
-
-Copyright 2008-2009 Joe Ferris and thoughtbot[http://www.thoughtbot.com], inc.

data/vendor/gems/factory_girl-1.2.3/Rakefile

@@ -1,81 +0,0 @@
-require 'rubygems'
-require 'rake'
-require 'rake/rdoctask'
-require 'rake/gempackagetask'
-require 'rcov/rcovtask'
-require 'date'
-
-require 'spec/rake/spectask'
-require 'cucumber/rake/task'
-
-desc 'Default: run the specs and features.'
-task :default => [:spec, :features]
-
-Spec::Rake::SpecTask.new do |t|
-  t.spec_opts = ['--options', "spec/spec.opts"]
-end
-
-desc 'Performs code coverage on the factory_girl plugin.'
-Rcov::RcovTask.new do |t|
-  t.test_files = FileList['spec/*_spec.rb']
-  t.verbose = true
-end
-
-desc 'Generate documentation for the factory_girl plugin.'
-Rake::RDocTask.new(:rdoc) do |rdoc|
-  rdoc.rdoc_dir = 'rdoc'
-  rdoc.title    = 'Factory Girl'
-  rdoc.options << '--line-numbers' << "--main" << "README.rdoc"
-  rdoc.rdoc_files.include('README.rdoc')
-  rdoc.rdoc_files.include('CONTRIBUTION_GUIDELINES.rdoc')
-  rdoc.rdoc_files.include('lib/**/*.rb')
-end
-
-desc 'Update documentation on website'
-task :sync_docs => 'rdoc' do
-  `rsync -ave ssh rdoc/ dev@dev.thoughtbot.com:/home/dev/www/dev.thoughtbot.com/factory_girl`
-end
-
-spec = Gem::Specification.new do |s|
-  s.name        = %q{factory_girl}
-  s.version     = "1.2.3"
-  s.summary     = %q{factory_girl provides a framework and DSL for defining and
-                     using model instance factories.}
-  s.description = %q{factory_girl provides a framework and DSL for defining and
-                     using factories - less error-prone, more explicit, and
-                     all-around easier to work with than fixtures.}
-
-  s.files        = FileList['[A-Z]*', 'lib/**/*.rb', 'spec/**/*.rb']
-  s.require_path = 'lib'
-  s.test_files   = Dir[*['spec/**/*_spec.rb']]
-
-  s.has_rdoc         = true
-  s.extra_rdoc_files = ["README.rdoc"]
-  s.rdoc_options = ['--line-numbers', "--main", "README.rdoc"]
-
-  s.authors = ["Joe Ferris"]
-  s.email   = %q{jferris@thoughtbot.com}
-  s.homepage = "http://thoughtbot.com/projects/factory_girl"
-
-  s.platform = Gem::Platform::RUBY
-end
-
-Rake::GemPackageTask.new spec do |pkg|
-  pkg.need_tar = true
-  pkg.need_zip = true
-end
-
-desc "Clean files generated by rake tasks"
-task :clobber => [:clobber_rdoc, :clobber_package]
-
-desc "Generate a gemspec file"
-task :gemspec do
-  File.open("#{spec.name}.gemspec", 'w') do |f|
-    f.write spec.to_ruby
-  end
-end
-
-Cucumber::Rake::Task.new(:features) do |t|
-  t.fork = true
-  t.cucumber_opts = ['--format', (ENV['CUCUMBER_FORMAT'] || 'progress')]
-end

data/vendor/gems/factory_girl-1.2.3/lib/factory_girl/aliases.rb

@@ -1,50 +0,0 @@
-class Factory
-
-  class << self
-    attr_accessor :aliases #:nodoc:
-  end
-  self.aliases = [
-    [/(.*)_id/, '\1'],
-    [/(.*)/, '\1_id']
-  ]
-
-  # Defines a new alias for attributes.
-  #
-  # Arguments:
-  # * pattern: +Regexp+
-  #   A pattern that will be matched against attributes when looking for
-  #   aliases. Contents captured in the pattern can be used in the alias.
-  # * replace: +String+
-  #   The alias that results from the matched pattern. Captured strings can
-  #   be substituded like with +String#sub+.
-  #
-  # Example:
-  #   
-  #   Factory.alias /(.*)_confirmation/, '\1'
-  #
-  # factory_girl starts with aliases for foreign keys, so that a :user
-  # association can be overridden by a :user_id parameter:
-  #
-  #   Factory.define :post do |p|
-  #     p.association :user
-  #   end
-  #
-  #   # The user association will not be built in this example. The user_id
-  #   # will be used instead.
-  #   Factory(:post, :user_id => 1)
-  def self.alias (pattern, replace)
-    self.aliases << [pattern, replace]
-  end
-
-  def self.aliases_for (attribute) #:nodoc:
-    aliases.collect do |params|
-      pattern, replace = *params
-      if pattern.match(attribute.to_s)
-        attribute.to_s.sub(pattern, replace).to_sym
-      else
-        nil
-      end
-    end.compact << attribute
-  end
-
-end

data/vendor/gems/factory_girl-1.2.3/lib/factory_girl/attribute/association.rb

@@ -1,20 +0,0 @@
-class Factory
-  class Attribute #:nodoc:
-
-    class Association < Attribute  #:nodoc:
-
-      attr_reader :factory
-
-      def initialize(name, factory, overrides)
-        super(name)
-        @factory   = factory
-        @overrides = overrides
-      end
-
-      def add_to(proxy)
-        proxy.associate(name, @factory, @overrides)
-      end
-    end
-
-  end
-end

data/vendor/gems/factory_girl-1.2.3/lib/factory_girl/attribute/callback.rb

@@ -1,16 +0,0 @@
-class Factory
-  class Attribute #:nodoc:
-
-    class Callback < Attribute  #:nodoc:
-      def initialize(name, block)
-        @name  = name.to_sym
-        @block = block
-      end
-
-      def add_to(proxy)
-        proxy.add_callback(name, @block)
-      end
-    end
-
-  end
-end

data/vendor/gems/factory_girl-1.2.3/lib/factory_girl/attribute/dynamic.rb

@@ -1,20 +0,0 @@
-class Factory
-  class Attribute #:nodoc:
-
-    class Dynamic < Attribute  #:nodoc:
-      def initialize(name, block)
-        super(name)
-        @block = block
-      end
-
-      def add_to(proxy)
-        value = @block.arity.zero? ? @block.call : @block.call(proxy)
-        if Factory::Sequence === value
-          raise SequenceAbuseError
-        end
-        proxy.set(name, value)
-      end
-    end
-
-  end
-end

data/vendor/gems/factory_girl-1.2.3/lib/factory_girl/attribute/static.rb

@@ -1,17 +0,0 @@
-class Factory
-  class Attribute #:nodoc:
-
-    class Static < Attribute  #:nodoc:
-
-      def initialize(name, value)
-        super(name)
-        @value = value
-      end
-
-      def add_to(proxy)
-        proxy.set(name, @value)
-      end
-    end
-
-  end
-end

data/vendor/gems/factory_girl-1.2.3/lib/factory_girl/attribute.rb

@@ -1,29 +0,0 @@
-class Factory
-
-  # Raised when defining an invalid attribute:
-  # * Defining an attribute which has a name ending in "="
-  # * Defining an attribute with both a static and lazy value
-  # * Defining an attribute twice in the same factory
-  class AttributeDefinitionError < RuntimeError
-  end
-  
-  class Attribute #:nodoc:
-
-    attr_reader :name
-
-    def initialize(name)
-      @name = name.to_sym
-
-      if @name.to_s =~ /=$/
-        attribute_name = $`
-        raise AttributeDefinitionError, 
-          "factory_girl uses 'f.#{attribute_name} value' syntax " +
-          "rather than 'f.#{attribute_name} = value'"
-      end
-    end
-
-    def add_to(proxy)
-    end
-  end
-
-end