active_mocker 1.7 → 1.7.1rc

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 47bbf4bb84a0ad4915e6347ee490f4d6b816f12a
-  data.tar.gz: c420efb807b35fed46902e3a9f284c3d28d695ee
+  metadata.gz: 27a581cdb90182c0e21fcb680a43e42ebe573a9c
+  data.tar.gz: 31b9e9a16588f87d64fa267542a5434dd752fd27
 SHA512:
-  metadata.gz: d0a37c3da9214f4628f4c746fe89512bd3468abc7130c26e388b6a6ea770d942b972162a9570c688916e7022c1c78172177405732e104a026668a2b2a7ed4f1c
-  data.tar.gz: 547eb65b75b51942e58ba6f998723d567dd15c6e38ec5f5851dcbbb546b60c5c5d24c499cb9bcb78d112dee08a11aecec6eac0cb22fbd773be127b5ed79c1dd6
+  metadata.gz: ed95a5fa4681cb5f2187693f4b95ed02e86867bf2bfe3e9f3684713aec0a22ae5fa9721373c9acb225b7d64d4378fa79859974299403cad0c957a6e55e3c331f
+  data.tar.gz: 4a951442f8a0fb1b3c0a1c505687af5f97163ae877039cf5a3f1c2e86de731b3d321af3dea969d5e347c220f71ee97cf97cd016ff896e093da308478ce6cd1f6

data/CHANGELOG.md

@@ -1,34 +1,20 @@
 # Changelog
 All notable changes to this project will be documented in this file.
 
-## 1.7rc2 - 2014-10-10
+## 1.7.1rc - 2014-10-19
 
 ### Enhancement
-- Now will regenerate mock after `rake db:rollback`.
-- Check added to see if mock was created with same running gem version of ActiveMocker. If they are not the same it will raise an error informing you to run `rake active_mocker:build`.
-- belong_to and has_one relationships when assigned will in most cases assign it's self to the corresponding has_many or like association. See `test_rails_4_app/spec/active_record_compatible_api.rb` for supported detail of supported ActiveRecord features.
-
-### Removed
-- `ActiveMocker::Mock::Config.experimental` flag has been removed, these are now on by default.
-
-## Added
-- Class method `table_name`.
-
-## 1.7.beta3 - 2014-09-25
+- Now works with Rails versions: 4.0, 4.1, 4.2beta2.
 
 ### Fix
-- Last beta introduced a bug where after assigning some associations they could not be read. Solution was to never access @associations directly inside mock. 
-
-## 1.7.beta2 - 2014-09-18
-
-### Fix 
-- Bug where creating record with an id could cause a duplicate id error.
-- Issue whenever an ActiveRecord Model has no schema behind it.
-- Issue assigning association would fail, added guard to @associations to only read and write symbols.
+- Issue when a relation had a scope defined by proc it would fail.
 
-## 1.7.beta1 - 2014-09-06
+## 1.7 - 2014-10-14
 
 ### Enhancement
+- Now will regenerate mock after `rake db:rollback`.
+- Check added to see if mock was created with same running gem version of ActiveMocker. If they are not the same it will raise an error informing you to run `rake active_mocker:build`.
+- belong_to and has_one relationships when assigned will in most cases assign it's self to the corresponding has_many or like association. See `test_rails_4_app/spec/active_record_compatible_api.rb` for supported detail of supported ActiveRecord features.
 - A class that Inherits a model now has the table of the parent.
 - Use this option if you need to modify where the mock generation hooks into. `ActiveMocker::Config.model_base_classes = %w[ ActiveRecord::Base ]`
 - When running `rake active_mocker:build` it will display the number of mocks that failed.
@@ -37,16 +23,22 @@ All notable changes to this project will be documented in this file.
 - Will create own log file `log/active_mocker.log` it will be cleared on each generation.
 - Attributes, associations, and scopes will now inherit from their parent class.
 
-###Removed
+### Removed
+- `ActiveMocker::Mock::Config.experimental` flag has been removed, these are now on by default.
 - Remove deprecated option `ActiveMocker.mock`
 - Remove Experimental feature reload
 - Remove experimental flag for set foreign_key on collection for has_many, belongs_to, and has_one.
 
-### Added
+## Added
+- Class method `table_name`.
 - Initialization of an abstract class will raise an error.
 - `record._create_caller_locations` for debugging obj’s creation location.
 
 ### Fix
+- Last beta introduced a bug where after assigning some associations they could not be read. Solution was to never access @associations directly inside mock. 
+- Bug where creating record with an id could cause a duplicate id error.
+- Issue whenever an ActiveRecord Model has no schema behind it.
+- Issue assigning association would fail, added guard to @associations to only read and write symbols.
 - Issue where using table names as the model file would replace a parent class with a child class that had the same table.
 
 ## 1.6.3 - 2014-08-14

data/README.md

@@ -5,7 +5,7 @@
 [![Dependency Status](https://gemnasium.com/zeisler/active_mocker.svg)](https://gemnasium.com/zeisler/active_mocker)
 [![Gitter chat](https://badges.gitter.im/zeisler/active_mocker.png)](https://gitter.im/zeisler/active_mocker)
 
-ActiveMocker creates mocks classes from ActiveRecord models. Allowing your test suite to run very fast by not loading Rails or hooking to a database. It parses the schema.rb and the defined methods on a model then generates a ruby file that can be included within a test. The mock file can be run by themselves and come with a partial implementation of ActiveRecord. Attributes and associations can be used just the same as in ActiveRecord. Methods will have the correct arguments but raise an NotImplementedError when called. Mocks are regenerated when the schema is modified so your mocks will not go stale; preventing the case where your units tests pass but production code fails.
+ActiveMocker creates mocks classes from ActiveRecord models. Allowing your test suite to run very fast by not loading Rails a database. It parses the schema.rb and the defined methods on a model then generates a ruby file that can be included within a test. The mock file can be run by themselves and come with a partial implementation of ActiveRecord. Attributes and associations can be used just the same as in ActiveRecord. Methods will have the correct arguments but raise an NotImplementedError when called. Mocks are regenerated when the schema is modified so your mocks will not go stale; preventing the case where your units tests pass but production code fails.
 
 Examples from a real apps
 
@@ -63,7 +63,7 @@ Or install it yourself as:
     $ gem install active_mocker
 
 ## Dependencies
-* Tested with Rails 4.1 may work with older versions but not supported.
+* Tested with Rails 4.0, 4.1, 4.2beta2
 * Requires Ruby MRI >= 2.1.
 
 

data/lib/active_mocker/active_record/relationships.rb

@@ -34,7 +34,6 @@ module ActiveMocker
 
         def initialize(name, options={})
           @name = name
-          @options = options.reduce(HashWithIndifferentAccess.new, :merge)
         end
 
         def options

data/lib/active_mocker/version.rb

@@ -1,3 +1,3 @@
 module ActiveMocker
-  VERSION = "1.7"
+  VERSION = "1.7.1rc"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: active_mocker
 version: !ruby/object:Gem::Version
-  version: '1.7'
+  version: 1.7.1rc
 platform: ruby
 authors:
 - Dustin Zeisler
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-10-14 00:00:00.000000000 Z
+date: 2014-10-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '4.1'
+        version: '4.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '4.1'
+        version: '4.0'
 - !ruby/object:Gem::Dependency
   name: virtus
   requirement: !ruby/object:Gem::Requirement
@@ -150,20 +150,6 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.3'
-- !ruby/object:Gem::Dependency
-  name: rails
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '4.1'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '4.1'
 - !ruby/object:Gem::Dependency
   name: rspec-rails
   requirement: !ruby/object:Gem::Requirement
@@ -226,51 +212,37 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2'
+        version: '2.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2'
+        version: '2.0'
 - !ruby/object:Gem::Dependency
-  name: debase
+  name: appraisal
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.0'
-- !ruby/object:Gem::Dependency
-  name: ruby-debug-ide
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.4'
+        version: '1.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.4'
+        version: '1.0'
 description: ActiveMocker creates mocks classes from ActiveRecord models. Allowing
-  your test suite to run very fast by not loading Rails or hooking to a database.
-  It parses the schema.rb and the defined methods on a model then generates a ruby
-  file that can be included within a test. The mock file can be run by themselves
-  and come with a partial implementation of ActiveRecord. Attributes and associations
-  can be used just the same as in ActiveRecord. Methods will have the correct arguments
-  but raise an Unimplemented error when called. Mocks are regenerated when the schema
-  is modified so your mocks will not go stale; preventing the case where your units
-  tests pass but production code fails.
+  your test suite to run very fast by not loading Rails or a database. It parses the
+  schema.rb and the defined methods on a model then generates a ruby file that can
+  be included within a test. The mock file can be run by themselves and come with
+  a partial implementation of ActiveRecord. Attributes and associations can be used
+  just the same as in ActiveRecord. Methods will have the correct arguments but raise
+  an NotImplementedError when called. Mocks are regenerated when the schema is modified
+  so your mocks will not go stale; preventing the case where your units tests pass
+  but production code fails.
 email:
 - dustin@zive.me
 executables: []
@@ -342,14 +314,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.1.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - ">"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.2.2
 signing_key: 
 specification_version: 4
 summary: Creates mocks from Active Record models. Allows your test suite to run very
-  fast by not loading Rails or hooking to a database.
+  fast by not loading Rails or a database.
 test_files: []