That was quick! Thanks Nathan. I tried out the fix and confirmed that it fixed my test case and now I am back in business.
On Nov 17, 11:21 pm, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > No need - I've just fixed this in r8f85cfd in stable and master. The > issue was that we were using || to choose between symbol locals and > string locals, and that interacted badly with false. > > Chris Eppstein wrote: > > If you can find and fix the bug, we'll gladly accept a patch. > > > Chris > > > On Mon, Nov 17, 2008 at 4:35 PM, scottwb <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > I have found that when I render a partial with a value in the :locals > > that is a boolean false, that it gets set to nil in the partial, > > instead of preserving it as false as I would have expected, and as is > > done when rendering an rhtml partial. > > > I wrote up a summary of this with some sample code at: > > http://sleeplesscoding.blogspot.com/2008/11/bug-in-haml-partial-rende... > > > Has anyone else seen this problem? Is this by design or is it a bug, > > or is there a supported workaround? > > > I have some old rhtml partials that I am converting to haml that rely > > on knowing the difference between false and nil for a passed in local, > > and hopefully I don't have to go through and change the way that code > > works... > > > Thanks, > > -scottwb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
