Labyricorn/liquid
1
0
Fork 0
mirror of https://github.com/Shopify/liquid.git synced 2026-09-19 10:52:48 -07:00
Code Issues Packages Projects Releases Wiki Activity

Migrated from getting-liquid-to-work-in-rails v5

RichMorin
2010-08-12 13:45:48 -07:00
parent ebc9c1fa1f
commit fa2aad914f
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Getting-Liquid-to-Work-in-Rails.textile
+9 -9
@@ -13,18 +13,18 @@ Liquid's Rails plugin tries to use your helpers as Filters.
Your helpers will always receive the piped-in text as the first parameter, and then any Filter parameters (passed after the colon). Your helpers will always receive the piped-in text as the first parameter, and then any Filter parameters (passed after the colon).
Helper: Helper:
<pre><code> <pre>
module ApplicationHelper module ApplicationHelper
def truncate(input, length) def truncate(input, length)
input[0..length] + '...' input[0..length] + '...'
end end
end end
</pre></code> </pre>
Liquid: Liquid:
<pre><code> <pre>
{{ 'This is a long section of text' | truncate: 3 }} #=> Thi... {{ 'This is a long section of text' | truncate: 3 }} #=> Thi...
</pre></code> </pre>
h2. Using Rails model data and methods in Liquid templates h2. Using Rails model data and methods in Liquid templates
@@ -35,11 +35,11 @@ If you'd like to pass your ActiveRecord (or other) objects to a Liquid template,
The easy way is to add a @liquid_methods@ call: The easy way is to add a @liquid_methods@ call:
<pre><code> <pre>
class Post < ActiveRecord::Base class Post < ActiveRecord::Base
liquid_methods :title, :body, :comments liquid_methods :title, :body, :comments
... ...
</pre></code> </pre>
"Behind the scenes":http://github.com/tobi/liquid/tree/master/lib/liquid/module_ex.rb, "Behind the scenes":http://github.com/tobi/liquid/tree/master/lib/liquid/module_ex.rb,
@liquid_methods@ actually constructs a "Liquid Drop":http://liquid.rubyforge.org/classes/Liquid/Drop.html with the methods you include. This way, you have lazy loading (say, of associated models such as "comments" in the example above) of methods. @liquid_methods@ actually constructs a "Liquid Drop":http://liquid.rubyforge.org/classes/Liquid/Drop.html with the methods you include. This way, you have lazy loading (say, of associated models such as "comments" in the example above) of methods.
@@ -47,13 +47,13 @@ class Post < ActiveRecord::Base
An alternate route is to add a @to_liquid@ call in your object, An alternate route is to add a @to_liquid@ call in your object,
returning either one of the types listed above (string, array, hash, etc) or an object that in turn responds to @to_liquid@. returning either one of the types listed above (string, array, hash, etc) or an object that in turn responds to @to_liquid@.
<pre><code> <pre>
class Post < ActiveRecord::Base class Post < ActiveRecord::Base
... ...
def to_liquid def to_liquid
{'title' => title, 'body' => body} {'title' => title, 'body' => body}
end end
</pre></code> </pre>
Finally, you can write and register a completely new "Liquid Drop":http://liquid.rubyforge.org/classes/Liquid/Drop.html class. Finally, you can write and register a completely new "Liquid Drop":http://liquid.rubyforge.org/classes/Liquid/Drop.html class.
This enables you to pull from various models and helps you consolidate (lazy-loaded) methods used just for passing data to templates. This enables you to pull from various models and helps you consolidate (lazy-loaded) methods used just for passing data to templates.