performify 0.4.0 → 0.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a96ab69ab79f8f0b99f818b762c932b86d31ecc6
-  data.tar.gz: 58b169f4eccdffbb8caf2fddee1c5b89bb4369d4
+  metadata.gz: a683e8557fe63bce6b47dc99f35e9df354f1df02
+  data.tar.gz: 6ccd6d959c82eddae847f73c531e1fc8bd8f8d89
 SHA512:
-  metadata.gz: 1a1e944109d8ad0205d7080234a9073031f98af811c6b90aa018564661fd435c75952393c580e10a1881996eef203bbec337e38105199f4e3f1934162a3b2c3a
-  data.tar.gz: 82897b5b49b010f89481da7c23dda87f200b22f2e0ad7d63719aeb87ba99584cc10f92f5b697c51595eac21a074a5f4d050e793cab584ba6b065f45a6778b00a
+  metadata.gz: ab7e975a64c0877e3e7fccb9e1fff3669288621c92d84f2007b6e34c110e672f089ba771581726ffcfcb919909e86b9b480797e0808c396b37ace33b6f8a133e
+  data.tar.gz: d911869f274a6e69d26f29ffd5998bad0ffe4bdbbf811f1837204768665f68d44b26b221e5d36c4fd4d7c10222997d80990d9fe3f89629e3b43e3d401fe1e417

data/README.md

@@ -32,6 +32,7 @@ How to have a deal with services:
 4. Use `super` to work with db transaction and automatic success / fail workflow control
 5. Use `success!` and `fail!` to control everything by hands
 6. Use `on_success` / `on_fail` to define callbacks
+7. Use `schema do ... end` if you want to use validations
 
 ### ApplicationService
 
@@ -182,7 +183,7 @@ Performify allows you to validate input arguments using [dry-validation](http://
 
 ```ruby
 module Users
-  module Create
+  class Create
     schema do
       required(:email).filled(:str?)
     end
@@ -204,7 +205,7 @@ Sometimes you can have differences between validation errors and execution error
 
 ```ruby
 module Users
-  module Create
+  class Create
     attr_reader :user
 
     schema do
@@ -241,6 +242,43 @@ else
 end
 ```
 
+## Initialization
+
+Performify will dynamically define accessors for all arguments passed to service in addition to current_user:
+
+```ruby
+module Users
+  class Create
+    def execute!
+      # it will define accessors for all arguments:
+      User.new(email: email, role: role, manager: current_user)
+    end
+  end
+end
+
+service = Users::Create.new(current_user, email: 'mail@google.com', role: 'employee')
+```
+
+But if you use `schema` to validate parameters Performify will define accessors only for additional arguments mentioned in schema:
+
+```ruby
+module Users
+  class Create
+    schema do
+      required(:email).filled(:str?)
+      optional(:phone).filled(:str?)
+    end
+
+    def execute!
+      # it will define accessors for `email` and `phone`, but won't define `role`
+      User.new(email: email, phone: phone, manager: current_user) # phone is nil
+    end
+  end
+end
+
+service = Users::Create.new(current_user, email: 'mail@google.com', role: 'manager')
+```
+
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `bin/rspec spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.

data/lib/performify/base.rb

@@ -16,8 +16,6 @@ module Performify
         super(&block)
       end
 
-      return if args.empty?
-
       validate(args)
       define_singleton_methods(args)
 

data/lib/performify/version.rb

@@ -1,3 +1,3 @@
 module Performify
-  VERSION = '0.4.0'.freeze
+  VERSION = '0.4.1'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: performify
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
 platform: ruby
 authors:
 - Sergey Tsvetkov
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2017-10-12 00:00:00.000000000 Z
+date: 2017-10-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord