eventosaurus 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1a8ef4f20b8d48c0c0e035f514ba4088578e9068
-  data.tar.gz: 9038157130f2b42586d4fee746a3ebd394d3d0c2
+  metadata.gz: 599ff59a55cf9f34dc2c1fce3b3ef8e605bc2aee
+  data.tar.gz: 832ae4467408a064116a2335ba9e41fefc923c30
 SHA512:
-  metadata.gz: 90643659fb8232e9f6d713d946adbd8f984d49038d00a9095bd30a79df287796603ffcb449104ea79829f8f4944dd0906d5a204742d72a66579739d8888116a9
-  data.tar.gz: 158959e5a2f144a853cf7fa300301dde2d08dc742143b98ab826984ee081d79981d9a40a73df7bce2b38d28602e10e94cfcfd076fc6000c504c1bc171b50cb02
+  metadata.gz: 393946457e9f53cc08e65c1b9e42284840280039aac1c0777298bec8210b07047761d25c56cd986b11cd682151277632771023c30c387eb296839877fb74d7cf
+  data.tar.gz: 2f6234c2b220187f760d3d03d5cc5ab0f26299b3927d6846980e4a1038b22353889368f34787c5535b7297d4bd6d1b49aacfb54688b43c437ab6be85b332c5e7

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+# 1.0.1
+
+* updates test_mode methods to accept any number of arguments
+
 # 1.0.0
 
 * changes name to 'eventosaurus'

data/README.md

@@ -127,7 +127,7 @@ There are some built-in attributes for your events:
 
 ## Building the Tables
 
-DynamoDB must have the tables needed to run your events. Once you've written your event classes you must run a rake task to create the tables. The tables are namespaced by your environment, as defined in the environment_prefix variable mentioned above. So if you build locally, the table name might be `localhost_core_customer_audit`. This will allow us to quickly get up and running on new environments. For the time being, the rake task expects your event definitions to be in `app/models/events`. **Be sure to put them there!**. Rake tasks are scoped to only work with tables that begin with your environment_prefix. This means even if staging and production point to the same dynamodb account, the `drop_tables` task will only drop tables from the environment specified.
+DynamoDB must have the tables needed to run your events. Once you've written your event classes you must run a rake task to create the tables. The tables are namespaced by your environment, as defined in the environment_prefix variable mentioned above. So if you build locally, the table name might be `localhost_phone_call`. This will allow us to quickly get up and running on new environments. For the time being, the rake task expects your event definitions to be in `app/models/events`. **Be sure to put them there!**. Rake tasks are scoped to only work with tables that begin with your environment_prefix. This means even if staging and production point to the same dynamodb account, the `drop_tables` task will only drop tables from the environment specified.
 
 ```
 rake eventosaurus:create_tables
@@ -159,15 +159,12 @@ To store data use the `.store` class method on your event class. Use the same si
 
 ```ruby
 # Somewhere in your app:
- def check_for_audit(row)
-    if audit_time?
-      Events::CoreCustomerAudit.store(
-          updated_row: row,
-          updated_attribute: 'first_name',
-          updated_by_user_id: 35,
-          audit_occurred_at: UTC.now
+ def check_for_phonecall(row)
+      Events::PhoneCall.store(
+          person_id: row[:person_id],
+          phone_number: row[:phone_number],
+          last_called: row[:last_called]
       )
-    end
  end
 ```
 
@@ -176,17 +173,17 @@ To store data use the `.store` class method on your event class. Use the same si
 The gem gives you some dynamic methods to query your data based on your table definition. It's important to keep in mind that you are working with DynamoDB. It is not meant to be a data store that is accessed generically. It expects you to know the queries you want to run upfront. Good for us, we are storing each event type in its own table, so we can make good guesses about this. To this end, eventosaurus creates getters for the attributes you listed in your table definition:
 
 ```ruby
- Events::CoreCustomerAudit.by_customer_id(5)
- Events::CoreCustomerAudit.by_customer_id(5).by_table_name('users').count
+ Events::PhoneCall.by_person_id(5)
+ Events::PhoneCall.by_person_id(5).by_table_name('users').count
 
  # event_uuid & created_at included for free :)
- Events::CoreCustomerAudit.by_created_at('2015-01-04', 'GT')
+ Events::PhoneCall.by_created_at('2015-01-04', 'GT')
 ```
 
 The queries above return eventosaurus Query objects. To actually execute the query, use the `run` method:
 
 ```ruby
-Events::CoreCustomerAudit.by_customer_id(5).count.run
+Events::PhoneCall.by_person_id(5).count.run
 ```
 
 Note:
@@ -197,7 +194,7 @@ Note:
 
 ```
 # too many secondary predicates. after one secondary index is used, the rest will be full scans on whatever comes back after the first local index.
-Events::CoreCustomerAudit.by_created_at('2015-01-04', 'GT').by_table_name('users')
+Events::PhoneCall.by_created_at('2015-01-04', 'GT').by_table_name('users')
 ```
 
 **To sum it up: for speed, you are allowed 0||1 partition key condition and 0||1 secondary condition. No more than that.**

data/lib/eventosaurus.rb

@@ -6,5 +6,6 @@ require 'eventosaurus/configuration'
 require 'eventosaurus/storable'
 require 'eventosaurus/query_builder'
 require 'eventosaurus/services/table_manager_service'
+require 'eventosaurus/lib/test_mode'
 require 'eventosaurus/models/table.rb'
 require 'eventosaurus/models/query.rb'

data/lib/eventosaurus/configuration.rb

@@ -16,13 +16,11 @@ module Eventosaurus
     end
 
     def enable_test_mode
-      Storable::ClassMethods.redefine_method(:store) do
-        true
-      end
+      store = TestMode.instance_method(:store)
+      run = TestMode.instance_method(:run)
 
-      Models::Query.redefine_method(:run) do
-        true
-      end
+      Storable::ClassMethods.send(:define_method, :store, store)
+      Models::Query.send(:define_method, :run, run)
     end
   end
 

data/lib/eventosaurus/lib/test_mode.rb

@@ -0,0 +1,11 @@
+module Eventosaurus
+  module TestMode
+    def store(*_)
+      true
+    end
+
+    def run(*_)
+      true
+    end
+  end
+end

data/lib/eventosaurus/version.rb

@@ -1,7 +1,7 @@
 module Eventosaurus
   MAJOR = '1'.freeze
   MINOR = '0'.freeze
-  PATCH = '0'.freeze
+  PATCH = '1'.freeze
 
   VERSION = [MAJOR, MINOR, PATCH].join('.')
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: eventosaurus
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Blue Apron Engineering
@@ -175,6 +175,7 @@ files:
 - eventosaurus.gemspec
 - lib/eventosaurus.rb
 - lib/eventosaurus/configuration.rb
+- lib/eventosaurus/lib/test_mode.rb
 - lib/eventosaurus/models/query.rb
 - lib/eventosaurus/models/table.rb
 - lib/eventosaurus/persistors/sidekiq.rb
@@ -211,4 +212,3 @@ signing_key:
 specification_version: 4
 summary: Enables easy reporting of events to an event store.
 test_files: []
-has_rdoc: