mustache 0.9.2 → 0.10.0

data/README.md

@@ -8,7 +8,7 @@ As ctemplates says, "It emphasizes separating logic from presentation:
 it is impossible to embed application logic in this template language."
 
 For a list of implementations (other than Ruby) and tips, see
-<http://defunkt.github.com/mustache/>.
+<http://mustache.github.com/>.
 
 
 Overview
@@ -99,7 +99,7 @@ Tag Types
 
 For a language-agnostic overview of Mustache's template syntax, see
 the `mustache(5)` manpage or
-<http://defunkt.github.com/mustache/mustache.5.html>.
+<http://mustache.github.com/mustache.5.html>.
 
 
 Escaping
@@ -336,7 +336,7 @@ Command Line
 ------------
 
 See `mustache(1)` man page or
-<http://defunkt.github.com/mustache/mustache.1.html>
+<http://mustache.github.com/mustache.1.html>
 for command line docs.
 
 
@@ -347,10 +347,6 @@ Installation
 
     $ gem install mustache
 
-### [Rip](http://hellorip.com)
-
-    $ rip install git://github.com/defunkt/mustache.git
-
 
 Acknowledgements
 ----------------
@@ -362,13 +358,38 @@ Special thanks to [Magnus Holm](http://judofyr.net/) for all his
 awesome work on Mustache's parser.
 
 
+Contributing
+------------
+
+Once you've made your great commits:
+
+1. [Fork][fk] Mustache
+2. Create a topic branch - `git checkout -b my_branch`
+3. Push to your branch - `git push origin my_branch`
+4. Create an [Issue][is] with a link to your branch
+5. That's it!
+
+You might want to checkout Resque's [Contributing][cb] wiki page for information
+on coding standards, new features, etc.
+
+
+Mailing List
+------------
+
+To join the list simply send an email to <mustache@librelist.com>. This
+will subscribe you and send you information about your subscription,
+including unsubscribe information.
+
+The archive can be found at <http://librelist.com/browser/>.
+
+
 Meta
 ----
 
 * Code: `git clone git://github.com/defunkt/mustache.git`
-* Home: <http://defunkt.github.com/mustache>
+* Home: <http://mustache.github.com>
 * Bugs: <http://github.com/defunkt/mustache/issues>
-* List: <http://groups.google.com/group/mustache-rb>
+* List: <mustache@librelist.com>
 * Test: <http://runcoderun.com/defunkt/mustache>
 * Gems: <http://rubygems.org/gems/mustache>
 
@@ -379,3 +400,6 @@ You can also find us in `#{` on irc.freenode.net.
 [3]: http://google-ctemplate.googlecode.com/svn/trunk/doc/howto.html
 [4]: http://github.com/brynary/rack-bug/
 [5]: http://img.skitch.com/20091027-n8pxwwx8r61tc318a15q1n6m14.png
+[cb]: http://wiki.github.com/defunkt/resque/contributing
+[fk]: http://help.github.com/forking/
+[is]: http://github.com/defunkt/mustache/issues

data/Rakefile

@@ -94,7 +94,7 @@ task :pages => [ "man:build" ] do
   end
 
   `git commit -am 'generated manual'`
-  `git checkout gh-pages`
+  `git checkout site`
 
   Dir['*.newhtml'].each do |f|
     mv f, f.sub('.newhtml', '.html')
@@ -102,7 +102,7 @@ task :pages => [ "man:build" ] do
 
   `git add .`
   `git commit -m updated`
-  `git push origin gh-pages`
+  `git push site site:master`
   `git checkout master`
   puts :done
 end

data/bin/mustache

@@ -23,7 +23,7 @@ class Mustache
         opts.separator " "
 
         opts.separator "  See mustache(1) or " +
-          "http://defunkt.github.com/mustache/mustache.1.html"
+          "http://mustache.github.com/mustache.1.html"
         opts.separator "  for more details."
 
         opts.separator " "

data/lib/mustache/generator.rb

@@ -109,6 +109,23 @@ class Mustache
       compiled
     end
 
+    # Fired when we find an inverted section. Just like `on_section`,
+    # we're passed the inverted section name and the array of tokens.
+    def on_inverted_section(name, content)
+      # Convert the tokenized content of this section into a Ruby
+      # string we can use.
+      code = compile(content)
+
+      # Compile the Ruby for this inverted section now that we know
+      # what's inside.
+      ev(<<-compiled)
+      v = ctx[#{name.to_sym.inspect}]
+      if v.nil? || v == false || v.respond_to?(:empty?) && v.empty?
+        #{code}
+      end
+      compiled
+    end
+
     # Fired when the compiler finds a partial. We want to return code
     # which calls a partial at runtime instead of expanding and
     # including the partial's body to allow for recursive partials.

data/lib/mustache/parser.rb

@@ -45,7 +45,7 @@ EOF
     end
 
     # After these types of tags, all whitespace will be skipped.
-    SKIP_WHITESPACE = [ '#', '/' ]
+    SKIP_WHITESPACE = [ '#', '^', '/' ]
 
     # The content allowed in a tag name.
     ALLOWED_CONTENT = /(\w|[?!\/-])*/
@@ -75,6 +75,13 @@ EOF
 
     # Given a string template, returns an array of tokens.
     def compile(template)
+      if template.respond_to?(:encoding)
+        @encoding = template.encoding
+        template = template.dup.force_encoding("BINARY")
+      else
+        @encoding = nil
+      end
+
       # Keeps information about opened sections.
       @sections = []
       @result = [:multi]
@@ -102,7 +109,7 @@ EOF
       # Since {{= rewrites ctag, we store the ctag which should be used
       # when parsing this specific tag.
       current_ctag = self.ctag
-      type = @scanner.scan(/#|\/|=|!|<|>|&|\{/)
+      type = @scanner.scan(/#|\^|\/|=|!|<|>|&|\{/)
       @scanner.skip(/\s*/)
 
       # ANY_CONTENT tags allow any character inside of them, while
@@ -124,6 +131,11 @@ EOF
         @result << [:mustache, :section, content, block]
         @sections << [content, position, @result]
         @result = block
+      when '^'
+        block = [:multi]
+        @result << [:mustache, :inverted_section, content, block]
+        @sections << [content, position, @result]
+        @result = block
       when '/'
         section, pos, result = @sections.pop
         @result = result
@@ -173,6 +185,8 @@ EOF
         @scanner.clear
       end
 
+      text.force_encoding(@encoding) if @encoding
+
       @result << [:static, text]
     end
 

data/lib/mustache/sinatra.rb

@@ -70,7 +70,7 @@ class Mustache
 
           # If it's just an anonymous subclass then don't bother, otherwise
           # give us a layout instance.
-          if layout.name.empty?
+          if layout.name && layout.name.empty?
             layout = nil
           else
             layout = layout.new

data/lib/mustache/template.rb

@@ -15,6 +15,8 @@ class Mustache
   #
   # >> Mustache.render(template, hash)
   class Template
+    attr_reader :source
+
     # Expects a Mustache template as a string along with a template
     # path, which it uses to find partials.
     def initialize(source)

data/lib/mustache/version.rb

@@ -1,3 +1,3 @@
 class Mustache
-  Version = '0.9.2'
+  Version = '0.10.0'
 end

data/man/mustache.1.ron

@@ -124,4 +124,4 @@ Original CTemplate by Google
 ## SEE ALSO
 
 mustache(5), mustache(7), gem(1),
-<http://defunkt.github.com/mustache/>
+<http://mustache.github.com/>

data/man/mustache.5

@@ -65,13 +65,12 @@ replaced with a value, some nothing, and others a series of
 values. This document explains the different types of Mustache tags.
 .
 .SH "TAG TYPES"
-Tags are indicated by the double mustaches. \fB{{name}}\fR is a tag. Let's
-talk about the different types of tags.
+Tags are indicated by the double mustaches. \fB{{name}}\fR is a tag, as is \fB{{#name}}\fR. Let's talk about the different types of tags.
 .
 .SS "Variables"
 The most basic tag is the variable. A \fB{{name}}\fR tag in a basic
-template will try to call the \fBname\fR method on your view. If there is
-no \fBname\fR method, an exception will be raised.
+template will try to find the \fBname\fR key or method on your view. If
+there is no \fBname\fR method, nothing will be rendered.
 .
 .P
 All variables are HTML escaped by default. If you want to return
@@ -83,7 +82,8 @@ useful when changing delimiters (see "Set Delimter" below).
 .
 .P
 By default a variable "miss" returns an empty string. This can usually
-be configured in your Mustache library.
+be configured in your Mustache library. The Ruby version of Mustache
+supports raising an exception in this situation, for instance.
 .
 .P
 Template:
@@ -130,16 +130,27 @@ Output:
 .
 .IP "" 0
 .
-.SS "Boolean Sections"
+.SS "Sections"
+Sections render blocks of text one or more times, depending on the
+value of the referenced tag.
+.
+.P
 A section begins with a pound and ends with a slash. That is,\fB{{#person}}\fR begins a "person" section while \fB{{/person}}\fR ends it.
 .
 .P
-If the \fBperson\fR key exists and calling it returns false, the HTML
-between the pound and slash will not be displayed.
+If the \fBperson\fR key exists and calling it returns false or an empty
+list, the HTML between the pound and slash will not be displayed.
+.
+.P
+If the \fBperson\fR method exists and calling it returns true or an
+object, the HTML between the pound and slash will be rendered and
+displayed exactly one time. The object that was returned by the \fBperson\fR method will become the context of the block, as well.
 .
 .P
-If the \fBperson\fR method exists and calling it returns true, the HTML
-between the pound and slash will be rendered and displayed.
+If the \fBperson\fR method exists and calling it returns a non\-empty list,
+the text in the block will be displayed once for each item in the
+list. The context of the block will be set to the current item for
+each iteration. In this way we can loop over collections.
 .
 .P
 Template:
@@ -153,6 +164,9 @@ Template:
 {{#anything_else}}
   Never shown!
 {{/anything_else}}
+{{#repo}}
+  <b>{{name}}</b>
+{{/repo}}
 .
 .fi
 .
@@ -165,7 +179,12 @@ Hash:
 .
 .nf
 {
-  "person": true
+  "person": true,
+  "repo": [
+    { "name": "resque" },
+    { "name": "hub" },
+    { "name": "rip" },
+  ]
 }
 .
 .fi
@@ -179,21 +198,23 @@ Output:
 .
 .nf
 Shown!
+<b>resque</b>
+<b>hub</b>
+<b>rip</b>
 .
 .fi
 .
 .IP "" 0
 .
-.SS "Enumerable Sections"
-Enumerable sections are syntactically identical to boolean sections in
-that they begin with a pound and end with a slash. The difference,
-however, is in the view: if the method called returns an enumerable,
-the section is repeated as the enumerable is iterated over.
+.SS "Inverted Sections"
+An inverted section begins with a caret (hat) and ends with a
+slash. That is \fB{{^person}}\fR begins a "person" inverted section while \fB{{/person}}\fR ends it.
 .
 .P
-Each item in the enumerable is expected to be a hash which will then
-become the context of the corresponding iteration. In this way we can
-construct loops.
+While sections can be used to render text one or more times based on the
+value of the key given, inverted sections may render text once based
+on the inverse value of the key given. That is, they will be rendered
+if the key doesn't exist, is false, or is an empty list.
 .
 .P
 Template:
@@ -204,6 +225,9 @@ Template:
 {{#repo}}
   <b>{{name}}</b>
 {{/repo}}
+{{^repo}}
+  No repos :(
+{{/repo}}
 .
 .fi
 .
@@ -216,11 +240,7 @@ Hash:
 .
 .nf
 {
-  "repo": [
-    { "name": "resque" },
-    { "name": "hub" },
-    { "name": "rip" },
-  ]
+  "repo": []
 }
 .
 .fi
@@ -233,9 +253,7 @@ Output:
 .IP "" 4
 .
 .nf
-<b>resque</b>
-<b>hub</b>
-<b>rip</b>
+No repos :(
 .
 .fi
 .
@@ -269,9 +287,40 @@ Will render as follows:
 Partials begin with a greater than sign, like \fB{{> box}}\fR.
 .
 .P
-It is useful to think of partials as a "template expansion" \- that is,
-the actual partial tag will be replaced with the content of the
-partial. Therefor partials share the current context.
+Partials are rendered at runtime (as opposed to compile time), so
+recursive partials are possible. Just avoid infinite loops.
+.
+.P
+They also inherit the calling context. Whereas in ERB you may have
+this:
+.
+.IP "" 4
+.
+.nf
+<%= partial :next_more, :start => start, :size => size %>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Mustache requires only this:
+.
+.IP "" 4
+.
+.nf
+{{> next_more}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Why? Because the \fBnext_more.mustache\fR file will inherit the \fBsize\fR and \fBstart\fR methods from the calling context.
+.
+.P
+In this way you may want to think of partials as includes, or template
+expansion, even though it's not literally true.
 .
 .P
 For example, this template and partial:

data/man/mustache.5.html

@@ -106,14 +106,14 @@ values. This document explains the different types of Mustache tags.</p>
 
 <h2>TAG TYPES</h2>
 
-<p>Tags are indicated by the double mustaches. <code>{{name}}</code> is a tag. Let's
-talk about the different types of tags.</p>
+<p>Tags are indicated by the double mustaches. <code>{{name}}</code> is a tag, as is
+<code>{{#name}}</code>. Let's talk about the different types of tags.</p>
 
 <h3>Variables</h3>
 
 <p>The most basic tag is the variable. A <code>{{name}}</code> tag in a basic
-template will try to call the <code>name</code> method on your view. If there is
-no <code>name</code> method, an exception will be raised.</p>
+template will try to find the <code>name</code> key or method on your view. If
+there is no <code>name</code> method, nothing will be rendered.</p>
 
 <p>All variables are HTML escaped by default. If you want to return
 unescaped HTML, use the triple mustache: <code>{{{name}}}</code>.</p>
@@ -122,7 +122,8 @@ unescaped HTML, use the triple mustache: <code>{{{name}}}</code>.</p>
 useful when changing delimiters (see "Set Delimter" below).</p>
 
 <p>By default a variable "miss" returns an empty string. This can usually
-be configured in your Mustache library.</p>
+be configured in your Mustache library. The Ruby version of Mustache
+supports raising an exception in this situation, for instance.</p>
 
 <p>Template:</p>
 
@@ -148,16 +149,26 @@ be configured in your Mustache library.</p>
 * &lt;b&gt;GitHub&lt;/b&gt;
 </code></pre>
 
-<h3>Boolean Sections</h3>
+<h3>Sections</h3>
+
+<p>Sections render blocks of text one or more times, depending on the
+value of the referenced tag.</p>
 
 <p>A section begins with a pound and ends with a slash. That is,
 <code>{{#person}}</code> begins a "person" section while <code>{{/person}}</code> ends it.</p>
 
-<p>If the <code>person</code> key exists and calling it returns false, the HTML
-between the pound and slash will not be displayed.</p>
+<p>If the <code>person</code> key exists and calling it returns false or an empty
+list, the HTML between the pound and slash will not be displayed.</p>
+
+<p>If the <code>person</code> method exists and calling it returns true or an
+object, the HTML between the pound and slash will be rendered and
+displayed exactly one time. The object that was returned by the
+<code>person</code> method will become the context of the block, as well.</p>
 
-<p>If the <code>person</code> method exists and calling it returns true, the HTML
-between the pound and slash will be rendered and displayed.</p>
+<p>If the <code>person</code> method exists and calling it returns a non-empty list,
+the text in the block will be displayed once for each item in the
+list. The context of the block will be set to the current item for
+each iteration. In this way we can loop over collections.</p>
 
 <p>Template:</p>
 
@@ -167,54 +178,62 @@ between the pound and slash will be rendered and displayed.</p>
 {{#anything_else}}
   Never shown!
 {{/anything_else}}
+{{#repo}}
+  &lt;b&gt;{{name}}&lt;/b&gt;
+{{/repo}}
 </code></pre>
 
 <p>Hash:</p>
 
 <pre><code>{
-  "person": true
+  "person": true,
+  "repo": [
+    { "name": "resque" },
+    { "name": "hub" },
+    { "name": "rip" },
+  ]
 }
 </code></pre>
 
 <p>Output:</p>
 
 <pre><code>Shown!
+&lt;b&gt;resque&lt;/b&gt;
+&lt;b&gt;hub&lt;/b&gt;
+&lt;b&gt;rip&lt;/b&gt;
 </code></pre>
 
-<h3>Enumerable Sections</h3>
+<h3>Inverted Sections</h3>
 
-<p>Enumerable sections are syntactically identical to boolean sections in
-that they begin with a pound and end with a slash. The difference,
-however, is in the view: if the method called returns an enumerable,
-the section is repeated as the enumerable is iterated over.</p>
+<p>An inverted section begins with a caret (hat) and ends with a
+slash. That is <code>{{^person}}</code> begins a "person" inverted section while
+<code>{{/person}}</code> ends it.</p>
 
-<p>Each item in the enumerable is expected to be a hash which will then
-become the context of the corresponding iteration. In this way we can
-construct loops.</p>
+<p>While sections can be used to render text one or more times based on the
+value of the key given, inverted sections may render text once based
+on the inverse value of the key given. That is, they will be rendered
+if the key doesn't exist, is false, or is an empty list.</p>
 
 <p>Template:</p>
 
 <pre><code>{{#repo}}
   &lt;b&gt;{{name}}&lt;/b&gt;
 {{/repo}}
+{{^repo}}
+  No repos :(
+{{/repo}}
 </code></pre>
 
 <p>Hash:</p>
 
 <pre><code>{
-  "repo": [
-    { "name": "resque" },
-    { "name": "hub" },
-    { "name": "rip" },
-  ]
+  "repo": []
 }
 </code></pre>
 
 <p>Output:</p>
 
-<pre><code>&lt;b&gt;resque&lt;/b&gt;
-&lt;b&gt;hub&lt;/b&gt;
-&lt;b&gt;rip&lt;/b&gt;
+<pre><code>No repos :(
 </code></pre>
 
 <h3>Comments</h3>
@@ -233,9 +252,25 @@ construct loops.</p>
 
 <p>Partials begin with a greater than sign, like <code>{{&gt; box}}</code>.</p>
 
-<p>It is useful to think of partials as a "template expansion" - that is,
-the actual partial tag will be replaced with the content of the
-partial. Therefor partials share the current context.</p>
+<p>Partials are rendered at runtime (as opposed to compile time), so
+recursive partials are possible. Just avoid infinite loops.</p>
+
+<p>They also inherit the calling context. Whereas in ERB you may have
+this:</p>
+
+<pre><code>&lt;%= partial :next_more, :start =&gt; start, :size =&gt; size %&gt;
+</code></pre>
+
+<p>Mustache requires only this:</p>
+
+<pre><code>{{&gt; next_more}}
+</code></pre>
+
+<p>Why? Because the <code>next_more.mustache</code> file will inherit the <code>size</code> and
+<code>start</code> methods from the calling context.</p>
+
+<p>In this way you may want to think of partials as includes, or template
+expansion, even though it's not literally true.</p>
 
 <p>For example, this template and partial:</p>
 

data/man/mustache.5.ron

@@ -41,15 +41,15 @@ values. This document explains the different types of Mustache tags.
 
 ## TAG TYPES
 
-Tags are indicated by the double mustaches. `{{name}}` is a tag. Let's
-talk about the different types of tags.
+Tags are indicated by the double mustaches. `{{name}}` is a tag, as is
+`{{#name}}`. Let's talk about the different types of tags.
 
 
 ### Variables
 
 The most basic tag is the variable. A `{{name}}` tag in a basic
-template will try to call the `name` method on your view. If there is
-no `name` method, an exception will be raised.
+template will try to find the `name` key or method on your view. If
+there is no `name` method, nothing will be rendered.
 
 All variables are HTML escaped by default. If you want to return
 unescaped HTML, use the triple mustache: `{{{name}}}`.
@@ -58,7 +58,8 @@ You can also use `&` to unescape a variable: `{{& name}}`. This may be
 useful when changing delimiters (see "Set Delimter" below).
 
 By default a variable "miss" returns an empty string. This can usually
-be configured in your Mustache library.
+be configured in your Mustache library. The Ruby version of Mustache
+supports raising an exception in this situation, for instance.
 
 Template:
 
@@ -81,16 +82,27 @@ Output:
     * <b>GitHub</b>
     * <b>GitHub</b>
 
-### Boolean Sections
+
+### Sections
+
+Sections render blocks of text one or more times, depending on the
+value of the referenced tag.
 
 A section begins with a pound and ends with a slash. That is,
 `{{#person}}` begins a "person" section while `{{/person}}` ends it.
 
-If the `person` key exists and calling it returns false, the HTML
-between the pound and slash will not be displayed.
+If the `person` key exists and calling it returns false or an empty
+list, the HTML between the pound and slash will not be displayed.
 
-If the `person` method exists and calling it returns true, the HTML
-between the pound and slash will be rendered and displayed.
+If the `person` method exists and calling it returns true or an
+object, the HTML between the pound and slash will be rendered and
+displayed exactly one time. The object that was returned by the
+`person` method will become the context of the block, as well.
+
+If the `person` method exists and calling it returns a non-empty list,
+the text in the block will be displayed once for each item in the
+list. The context of the block will be set to the current item for
+each iteration. In this way we can loop over collections.
 
 Template:
 
@@ -100,49 +112,58 @@ Template:
     {{#anything_else}}
       Never shown!
     {{/anything_else}}
+    {{#repo}}
+      <b>{{name}}</b>
+    {{/repo}}
 
 Hash:
 
     {
-      "person": true
+      "person": true,
+      "repo": [
+        { "name": "resque" },
+        { "name": "hub" },
+        { "name": "rip" },
+      ]
     }
 
 Output:
 
     Shown!
+    <b>resque</b>
+    <b>hub</b>
+    <b>rip</b>
+
 
-### Enumerable Sections
+### Inverted Sections
 
-Enumerable sections are syntactically identical to boolean sections in
-that they begin with a pound and end with a slash. The difference,
-however, is in the view: if the method called returns an enumerable,
-the section is repeated as the enumerable is iterated over.
+An inverted section begins with a caret (hat) and ends with a
+slash. That is `{{^person}}` begins a "person" inverted section while
+`{{/person}}` ends it.
 
-Each item in the enumerable is expected to be a hash which will then
-become the context of the corresponding iteration. In this way we can
-construct loops.
+While sections can be used to render text one or more times based on the
+value of the key given, inverted sections may render text once based
+on the inverse value of the key given. That is, they will be rendered
+if the key doesn't exist, is false, or is an empty list.
 
 Template:
 
     {{#repo}}
       <b>{{name}}</b>
     {{/repo}}
+    {{^repo}}
+      No repos :(
+    {{/repo}}
 
 Hash:
 
     {
-      "repo": [
-        { "name": "resque" },
-        { "name": "hub" },
-        { "name": "rip" },
-      ]
+      "repo": []
     }
 
 Output:
 
-    <b>resque</b>
-    <b>hub</b>
-    <b>rip</b>
+    No repos :(
 
 
 ### Comments
@@ -160,9 +181,23 @@ Will render as follows:
 
 Partials begin with a greater than sign, like `{{> box}}`.
 
-It is useful to think of partials as a "template expansion" - that is,
-the actual partial tag will be replaced with the content of the
-partial. Therefor partials share the current context.
+Partials are rendered at runtime (as opposed to compile time), so
+recursive partials are possible. Just avoid infinite loops.
+
+They also inherit the calling context. Whereas in ERB you may have
+this:
+
+    <%= partial :next_more, :start => start, :size => size %>
+
+Mustache requires only this:
+
+    {{> next_more}}
+
+Why? Because the `next_more.mustache` file will inherit the `size` and
+`start` methods from the calling context.
+
+In this way you may want to think of partials as includes, or template
+expansion, even though it's not literally true.
 
 For example, this template and partial:
 
@@ -220,4 +255,4 @@ Original CTemplate by Google
 ## SEE ALSO
 
 mustache(1), mustache(7), gem(1),
-<http://defunkt.github.com/mustache/>
+<http://mustache.github.com/>

data/test/fixtures/complex_view.mustache

@@ -11,6 +11,7 @@
   {{/item}}
   </ul>
 {{/list}}
-{{#empty}}
+
+{{^list}}
   <p>The list is empty.</p>
-{{/empty}}
+{{/list}}

data/test/fixtures/inverted_section.mustache

@@ -0,0 +1,7 @@
+{{^t}}
+  * first
+{{/t}}
+* {{two}}
+{{^t}}
+  * third
+{{/t}}

data/test/fixtures/inverted_section.rb

@@ -0,0 +1,14 @@
+$LOAD_PATH.unshift File.dirname(__FILE__) + '/../lib'
+require 'mustache'
+
+class InvertedSection < Mustache
+  self.path = File.dirname(__FILE__)
+
+  def t
+    false
+  end
+
+  def two
+    "second"
+  end
+end

data/test/fixtures/nested_objects.mustache

@@ -11,6 +11,7 @@
   {{/item}}
   </ul>
 {{/list}}
-{{#empty}}
+
+{{^list}}
   <p>The list is empty.</p>
-{{/empty}}
+{{/list}}

data/test/mustache_test.rb

@@ -57,6 +57,16 @@ rendered
 rendered
   end
 
+  def test_single_line_inverted_sections
+    html = %(<p class="flash-notice" {{^ flash }}style="display: none;"{{/ flash }}>)
+
+    instance = Mustache.new
+    instance.template = html
+    assert_equal <<-rendered.strip, instance.render
+<p class="flash-notice" style="display: none;">
+rendered
+  end
+
   def test_simple
     assert_equal <<-end_simple, Simple.render
 Hello Chris
@@ -123,6 +133,14 @@ end_template
 end_section
   end
 
+  def test_inverted_section
+    assert_equal <<-end_section.strip, InvertedSection.render.strip
+* first
+* second
+* third
+end_section
+  end
+
   def test_comments
     assert_equal "<h1>A Comedy of Errors</h1>\n", Comments.render
   end
@@ -393,4 +411,21 @@ rendered
 <h2>中文又来啦</h2>
 rendered
   end
+
+  def test_indentation
+    view = Mustache.new
+    view[:name] = 'indent'
+    view[:text] = 'puts :indented!'
+    view.template = <<template
+def {{name}}
+  {{text}}
+end
+template
+
+  assert_equal <<template, view.render
+def indent
+  puts :indented!
+end
+template
+  end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: mustache
 version: !ruby/object:Gem::Version 
-  version: 0.9.2
+  version: 0.10.0
 platform: ruby
 authors: 
 - Chris Wanstrath
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-03-29 00:00:00 -07:00
+date: 2010-04-02 00:00:00 -07:00
 default_executable: 
 dependencies: []
 
@@ -69,6 +69,8 @@ files:
 - test/fixtures/escaped.rb
 - test/fixtures/inner_partial.mustache
 - test/fixtures/inner_partial.txt
+- test/fixtures/inverted_section.mustache
+- test/fixtures/inverted_section.rb
 - test/fixtures/namespaced.mustache
 - test/fixtures/namespaced.rb
 - test/fixtures/nested_objects.mustache