jbuilder-jpartial 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 42e8fbd77867fa4d90c7d865f933b404a329f3fb
-  data.tar.gz: 3e7f13140faae6c03e01e9015aaff88fcc2883d9
+  metadata.gz: b3b16018a2a317dd73d9b7c335f36bb5617b4a71
+  data.tar.gz: 32a5d28866d2253646d97d6b7c88c4e47352f9f7
 SHA512:
-  metadata.gz: 534e7ce5e4c792f5dd3fd1a2d6658d02f83ceac15eb56f5b401c5577fc221a655d03487250f5d05885cde5156c31ab6cf9b469e32dda6c3dbcc5bc5ba321b43c
-  data.tar.gz: 466c8f6948aceeadd94cbfdda4a938510acf60d484e1140e34f3bd7afc48f24733076f0f2441e0314637b3dd041c923e6828c517ede6fd79bc1d360fc82c7fbd
+  metadata.gz: 3ae11bfc5c2936ab47a50b5875bcb8c481a75a582db3d0be1e300dd9586685688542910191ed0872db8654ed79aae45ffb1a970607ec65ef3e0b34e3df6bcd8c
+  data.tar.gz: 1642559e330f11d60c8dc6da29213e1642dc30e51fad449e75cc058da9b489b65f2fc7971419dc2e9bfec7115e5ff4e4adf06fb0e603ab6a03992f2293efde97

data/README.md

@@ -78,7 +78,7 @@ The result is faster rendering and lower memory usage, while still being able to
 
 Alternatively you can define all partials in one initializer file and call them wherever you need them: from within other partial definitions or anywhere you use `Jbuilder` in your views. The advantage here is fewer files, all partials in one place, and since they're initialized at start up, you don't need to call any additional view templates to render the partials. Using the same example as above:
 
-#### In `app/config/initializers/jbuilder-jpartial.rb`
+#### In `app/config/initializers/jpartial.rb`
 ```ruby
 Jbuilder::Jpartial.configure do |jpartial|
   jpartial._post do |post|
@@ -106,7 +106,7 @@ end
 
 Notice that when using this method, we don't make any calls like `json.partial! 'post'` at any point to define the partial before using it. All of the partials are already defined in the initializer file.
 
-The advantage is a couple fewer renders. The disadvantage is that helper methods that are available in the views are not available in the configuration file.
+The advantage is even fewer renders and faster responses. The only real disadvantage is it bucks the regular Rails partial conventions. C'est la vie.
 
 #### How?
 Each method you call on `jpartial`  defines a Jbuilder method of the same name. The objects you will pass to that method are yielded to the block. Inside the block you can use plain old Jbuilder syntax.

data/lib/jbuilder/jpartial/version.rb

@@ -1,5 +1,5 @@
 class Jbuilder
   module Jpartial
-    VERSION = '0.2.2'.freeze
+    VERSION = '0.2.3'.freeze
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jbuilder-jpartial
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - M. Simon Borg