mini_service 0.0.0 → 0.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4e819cb6201d5918ccdc7905773d5be0702ffedd68be9f124055213478af8987
-  data.tar.gz: d3bd75d54c0e92e3c7c4fa2a41cdcb60228106f627f21a20e5ffa9e8e3d8b11f
+  metadata.gz: 521aa07f48ec8e042961b602d497fa8cdc566d86f4260d20be9d6740dcee96cf
+  data.tar.gz: 72b008ade7364935850e3d53a14ca828e096848542f769d2757818aa2d5411e7
 SHA512:
-  metadata.gz: 43459572a9839d4ea529b76cb109f665e70b331ef77acf66f51e7040b5fd8de7adfdacad7ddcb338b1a9e0bb7af2302622079f3130792b4e8da6815a44fc2a01
-  data.tar.gz: 7a503cb92018de678a4aba44f6a04574ed54081e42d12fcd9c4ede1100e508caaad19ef1e929a4839578ef616bc73a7765e8422aa9837da9a29239fe191a9184
+  metadata.gz: 3b6846fa288706326ff07f4e82e7b51dc645abe70f91bf7f4761f6535f22cd7ae5165b87aada11be9672127aed719dfdbd58074dc8408f7a62439a789dc596d3
+  data.tar.gz: 57627ad9fb5d33b57b49de5263f6386876e54cc6507d1d5c52cdfb5c5ea0d34b685f8a5386021921c70d13521b00d8decacbf882da14865cf7e07e7e8e1d1b6d

data/README.md

@@ -1,6 +1,6 @@
 # MiniService
 MiniServices are a prototype from which to build single-functionality
- minimalistic services, aiming to
+minimalistic services, aiming to
 help you correctly modularize and isolate your processes making them easier to
 mantain and less prone to
 errors.
@@ -9,8 +9,8 @@ errors.
 Define them like this:
 ```ruby
 class ExampleService < MiniService::Base
-  mini_requires %i[a1 a2]
-  mini_allows %i[a3 a4]
+  mini_reqs %i[a1 a2]
+  mini_lets %i[a3 a4]
 
   private
 
@@ -24,9 +24,10 @@ Call them like this:
 ```ruby
 ExampleService.call(a1: 1, a2: 2) # or
 ExampleService.call(a1: 1, a2: 2, a3: 3, a4: 4)
-# Instance variables will be available for each key-value pair
-# so you can use @a1 inside perform if a1 is given in the args hash
+
 ```
+Instance variables will be available for each key-value pair
+so you can use `@a1` inside perform if `a1` is given in the `args` hash
 
 Adding `mini_reqs` will raise an error if you miss `reqd` arguments
 
@@ -39,7 +40,7 @@ You can create your own services by inheriting from `MiniService::Base` class.
 
 Your `MiniServices` should be used via their `call` method, providing arguments
 in a hash, like
-`ExampleService.call(p1: v1, p2: v2)` or `ExampleService.call(args)` with args
+`ExampleService.call(a1: 1, a2: 2)` or `ExampleService.call(args)` with args
 built elsewhere.
 
 This will automatically initialize your service with one `@instance_variable`

data/lib/mini_service/version.rb

@@ -1,3 +1,3 @@
 module MiniService
-  VERSION = '0.0.0'.freeze
+  VERSION = '0.0.1'.freeze
 end

data/mini_service.gemspec

@@ -8,7 +8,7 @@ Gem::Specification.new do |spec|
   spec.authors  = ['Rodrgo Andrés Contreras Vilina']
   spec.email    = ['roanvilina@gmail.com']
 
-  spec.summary  = 'Provides a simple service prototype class and its generator.'
+  spec.summary  = 'Provides a simple service prototype class.'
   spec.homepage = 'https://github.com/roanvilina/mini_service'
   spec.license  = 'MIT'
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mini_service
 version: !ruby/object:Gem::Version
-  version: 0.0.0
+  version: 0.0.1
 platform: ruby
 authors:
 - Rodrgo Andrés Contreras Vilina
@@ -126,5 +126,5 @@ requirements: []
 rubygems_version: 3.0.1
 signing_key: 
 specification_version: 4
-summary: Provides a simple service prototype class and its generator.
+summary: Provides a simple service prototype class.
 test_files: []