sho 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 125faf4a77feba4430c913006c9a0c594032492c
-  data.tar.gz: 48b7aef74a0acd727c7cfa848fa95f932e22504a
+  metadata.gz: 6824fa2e826773658bce36e4f33d23715d62651b
+  data.tar.gz: fbe63cdf11cc334f60d87558c0996e6e55614113
 SHA512:
-  metadata.gz: 8bf09de4470247c23f2cd1ab956d01996337c8e654337cd53fe20f8331bdab50027dd7c0d46ee0a40edf1baad9dc88bbec8550088f6c3a0293a4754119da5e29
-  data.tar.gz: a4f0689ca99551d70ef474b90d856321fc1894918ac280e9931b48cf57da8e1e46d551fec964b5fbfc689d38f16e6d467e8e93cf4f86c1f40db85ba53d03d626
+  metadata.gz: ac5a8af9cf6047cbcfdbada0732738fa4802b1c3defd84a25fb352bfa2f49ed269a459f80571bbb54cb3811eb6f08ea2865e9051322069ac9d6e25b1979f7c9c
+  data.tar.gz: 2049bebaa82fcef22b3ac50c82aeafe86b1cb72b201c9b8a6a5c3f4f38dc2101738e20932bc0e2b89e4c149070def8d89734f1af0f62205532cd856efd3fae2b

data/Changelog.md

@@ -0,0 +1,10 @@
+# Sho versions
+
+## 0.0.2 - 2018-06-27
+
+* `yield` in inline templates work (for small inline layouts) -- [@adam12](https://github.com/adam12).
+
+## 0.0.1 - 2018-06-10
+
+Initial!
+

data/README.md

@@ -48,8 +48,8 @@ You can think about the template as a _method body_, which immediately answers a
 * **How do I test it? How do I set all the context for testing?** Just as with regular method: just create an instance, and call the method, and test the result.
 * **But where do I put this method?** Wherever you wish! Sho does NOT insist on any particular architecture or code layout, which means you can experiment and evaluate several options, like:
   * embed rendering in controller/Sinatra app (or even model, if you want to be really naughty today!) for the very first 30-lines-long prototype, then move it elsewhere (like "Extract Method" refactoring pattern, you know?)
-  * embed rendering in your service (operation) objects, so
-  * make Users::List class with `#html`, `#atom` and `#json` methods and use it like `Users::List.new(scope).send(request.format)` or `User::List.send(request.format, scope)`
+  * embed rendering in your service (operation) objects, so corresponding forms and buttons would be nested in the operation, and reused in other places like `Product::Create.new(current_user).button`
+  * make `Users::List` class with `#html`, `#atom` and `#json` methods and use it like `Users::List.new(scope).send(request.format)` or `User::List.send(request.format, scope)`
   * make `Trailblazer::Cells`-like one-class-per-template objects to call them like `Users::HtmlList.new(scope).()`
   * ...switch between several of the approaches, or even combine them in the same app!
 

data/lib/sho/configurator.rb

@@ -113,12 +113,12 @@ module Sho
 
     def define_template_method(name, tilt, mandatory, optional, layout)
       arguments = ArgumentValidator.new(*mandatory, **optional)
-      @host.__send__(:define_method, name) do |**locals|
+      @host.__send__(:define_method, name) do |**locals, &block|
         locals = arguments.call(**locals)
         if layout
           __send__(layout) { tilt.render(self, **locals) }
         else
-          tilt.render(self, **locals)
+          tilt.render(self, **locals, &block)
         end
       end
     end

data/lib/sho/version.rb

@@ -3,7 +3,7 @@
 module Sho
   MAJOR = 0
   MINOR = 0
-  PATCH = 1
+  PATCH = 2
   PRE = nil
   VERSION = [MAJOR, MINOR, PATCH, PRE].compact.join('.')
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: sho
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
 platform: ruby
 authors:
 - Victor Shepelev
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-06-10 00:00:00.000000000 Z
+date: 2018-06-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: tilt
@@ -154,30 +154,30 @@ dependencies:
   name: rubocop
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.57.2
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.57.2
 - !ruby/object:Gem::Dependency
   name: rubocop-rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 1.27.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 1.27.0
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -214,6 +214,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- Changelog.md
 - README.md
 - lib/sho.rb
 - lib/sho/argument_validator.rb
@@ -239,7 +240,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.14
+rubygems_version: 2.6.10
 signing_key: 
 specification_version: 4
 summary: Experimental post-framework view library