eitil 0.3.5 → 0.3.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 56e99cc29a813ae79db47620342f21059e0ee2fc6ac57d3d1555472908d671e1
-  data.tar.gz: 9391db6351b7f43230b64c7c7fa5a78fb5f7b95055ab2103ed68e28dd6673dc7
+  metadata.gz: 92cb9e9c82e5a3bfac7cbc0b5f662428bac557a2c3abbca8e30c86d60174363a
+  data.tar.gz: 20c072c5d8b8ce2e055ff0635472a66fdb11ba4155d770ac3cd600be0c0892da
 SHA512:
-  metadata.gz: 45540a3818ba26d7197ce4ed9cd2e7ab1061d7889445566f583a1fa5f1b218a324ae484f968c4291017bb12ea30c7e69cea3765135d2de2a703eee8ba02b8f9f
-  data.tar.gz: bec07d5c24641ce1e24dc31c450d01b98ca2a28b13ea799f8b285e59f701e946ae362e69e2e9c3ecc99dc805ce8bc6e48325acd5f8f19c04ccd2fd894b1cb786
+  metadata.gz: 945e8da34ffe7c89a24c11d2c4f75f2861ed9355ed0ed0c6759cc57d63485d7bb37006be1c4cb4f1fa8c93d13a672b238f4c99ec3110001db917cdc4cc2e02e0
+  data.tar.gz: d0a0641152e75e6f100eda08f83a3b253d8d80dd570fb26d76a2649822180e0f3c834da64012bb5d0e61709163fc81dbc7986ec5fa04d8d74faa8fd6a7f290a9

data/README.md

@@ -227,14 +227,18 @@ The router wrapper is a single module which is automatically included into your
 
 ### Info
 
-The Eitil jobs wrapper enables you to create perform_later jobs on the fly, without the need to create a new class and file. The macro new_job accepts a :method as argument and defines a new method :method_job. The newly defined :method_job, when called, performs the orginal :method in the background. The new_job macro accepts both instance methods and singleton methods, which are defined within there own method scope.
+The Eitil jobs wrapper enables you to create perform_now and perform_later jobs on the fly, without the need to create a new class and file. The macro new_job accepts a :method as argument and defines a new method :method_job. The newly defined :method_job, when called, performs the orginal :method in the background. The new_job macro accepts both instance methods and singleton methods, which are defined within there own method scope. In contrast, the new_job_debugger macro defines a new :method_job_debugger method, which performs in the foreground.
 
 ### Job Macro
 
 ```ruby
-new_job(_method)
-# assuming a method :print_hello_world, call as: new_job :hello_world
-# => method :hello_world_job
+new_job(_method, *args, **kwargs)
+# assuming a method :hello_world, call as: new_job :hello_world
+# => defines :hello_world_job
+
+new_job_debugger(_method, *args, **kwargs)
+# assuming a method :hello_world, call as: new_job_debugger :hello_world
+# => defines :hello_world_job_debugger
 ```
 
 - method is 

data/config/initializers/wrappers/jobs/active_job_macros.rb

@@ -6,19 +6,47 @@ Kernel.module_eval do
   # being that 'id' works for objects that have a database record, while '_self'
   # works for non database supported instanes, such as an Exporter instance.
 
-  def new_job(_method)
+  def new_job(_method, *args, **kwargs)
 
     if instance_methods(false).include? _method
-      define_method "#{_method}_job" do |_self = nil|
-        Eitil::SingleMethodJob.perform_later(_class: self.class.to_s, _method: _method.to_s, id: safe_send(:id), _self: self.to_json)
+      define_method "#{_method}_job" do |_self = nil, *args, **kwargs|
+        
+        Eitil::SingleMethodJob.perform_later(
+          *args, _class: self.class.to_s, _method: _method.to_s, id: safe_send(:id), _self: self.to_json, **kwargs
+        )
       end
 
-    elsif singleton_methods(false).include? _method
-      define_singleton_method "#{_method}_job" do
-        Eitil::SingleMethodJob.perform_later(_class: to_s, _method: _method.to_s)
+    elsif singleton_methods(false).include? _method      
+      define_singleton_method "#{_method}_job" do |*args, **kwargs|
+       
+        Eitil::SingleMethodJob.perform_later(
+          *args, _class: to_s, _method: _method.to_s, **kwargs
+        )
       end
-    end  
+    end 
+  end
+
+  # BEWARE: This is an exact copy of the above method, except for .perform_now instead of .perform_later and the method's name.
+  # The reason for not using helper methods is to not unnecessarily fill and potentially fuck up the Kernel environment.
 
+  def new_job_debugger(_method, *args, **kwargs)
+
+    if instance_methods(false).include? _method
+      define_method "#{_method}_job_debugger" do |_self = nil, *args, **kwargs|
+        
+        Eitil::SingleMethodJob.perform_now(
+          *args, _class: self.class.to_s, _method: _method.to_s, id: safe_send(:id), _self: self.to_json, **kwargs
+        )
+      end
+
+    elsif singleton_methods(false).include? _method      
+      define_singleton_method "#{_method}_job_debugger" do |*args, **kwargs|
+       
+        Eitil::SingleMethodJob.perform_now(
+          *args, _class: to_s, _method: _method.to_s, **kwargs
+        )
+      end
+    end 
   end
 
 end

data/config/initializers/wrappers/jobs/single_method_job.rb

@@ -8,9 +8,7 @@ module Eitil
     # being that 'id' works for objects that have a database record, while '_self'
     # works for non database supported instanes, such as an Exporter instance.
 
-    def perform(_class:, _method:, id: nil, _self: nil)     
-      binding.pry
-
+    def perform(*args, _class:, _method:, id: nil, _self: nil, **kwargs)      
       object = 
         if id
           _class.constantize.find(id)
@@ -20,7 +18,7 @@ module Eitil
           _class.constantize
         end
 
-      object.send _method
+      object.send _method, *args, **kwargs
     end
   end
 end

data/lib/eitil/version.rb

@@ -1,3 +1,3 @@
 module Eitil
-  VERSION = '0.3.5'
+  VERSION = '0.3.6'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: eitil
 version: !ruby/object:Gem::Version
-  version: 0.3.5
+  version: 0.3.6
 platform: ruby
 authors:
 - Jurriaan Schrofer
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-05-31 00:00:00.000000000 Z
+date: 2021-06-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails