From 9563f0960247142c7d87a77830f857a5d745b46a Mon Sep 17 00:00:00 2001 From: enthooz Date: Tue, 2 Aug 2011 13:29:32 -0700 Subject: [PATCH] And making the link text reflect the same url. :) --- Trying-to-Understand-Drops.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Trying-to-Understand-Drops.textile b/Trying-to-Understand-Drops.textile index 5512f74..e7df05b 100644 --- a/Trying-to-Understand-Drops.textile +++ b/Trying-to-Understand-Drops.textile @@ -13,7 +13,7 @@ Here are the 'drops' Explanation of above code
Liquid accepts only a limited number of objects types i.e. Strings, Arrays, Hashes, Numerics, and Booleans. If we want to pass our Active Record object to liquid templates we have to define that logic explicitly(Liquid doesn't provide that functionality). -Basically there are three methods/ways to define that logic "http://wiki.github.com/tobi/liquid/getting-liquid-to-work-in-rails.":https://github.com/Shopify/liquid/wiki/Getting-Liquid-to-Work-in-Rails +Basically there are three methods/ways to define that logic "http://wiki.github.com/Shopify/liquid/getting-liquid-to-work-in-rails.":https://github.com/Shopify/liquid/wiki/Getting-Liquid-to-Work-in-Rails The above describe method will constructs a Liquid Drop with the methods you included. After including the above said stuff you will be able to access user's email and login in the liquid template ie {{ user.email }} and {{ user.login }}. Only email and login will be available in the liquid template (all other methods will not be accessible to liquid templates i.e. user.password ).