sass-twitter-bootstrap 0.1.0

data/docs/build/node_modules/hogan.js/test/mustache.js

@@ -0,0 +1,90 @@
+/*
+ *  Copyright 2011 Twitter, Inc.
+ *  Licensed under the Apache License, Version 2.0 (the "License");
+ *  you may not use this file except in compliance with the License.
+ *  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ *  Unless required by applicable law or agreed to in writing, software
+ *  distributed under the License is distributed on an "AS IS" BASIS,
+ *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ *  See the License for the specific language governing permissions and
+ *  limitations under the License.
+ */
+
+var doc = this['document'];
+var fs = require('fs');
+
+var passed = 0;
+var failed = 0;
+
+if (!this['output']) {
+  var output = function (string) {
+    return doc ? doc.write(string + '<br/>') : console.log(string);
+  };
+}
+
+var Hogan = require(__dirname + '/../lib/hogan');
+var template = fs.readFileSync(__dirname + '/../lib/template.js').toString();
+var compiler = fs.readFileSync(__dirname + '/../lib/compiler.js').toString();
+var mustache_wrapper = fs.readFileSync(__dirname + '/../wrappers/mustache.js.mustache').toString();
+
+// Create a Mustache.js emulator from the distribution template
+var engines = (new Function(Hogan.compile(mustache_wrapper).render({template: template, compiler: compiler}) +
+                                          '; return {Hogan: Hogan, Mustache: Mustache};'))();
+
+var Mustache = engines.Mustache;
+var Hogan2 = engines.Hogan;
+
+
+// sanity check
+is(Mustache.hasOwnProperty('to_html'), true, 'Mustache has to_html method.');
+
+// Check for Mustache.js partial resolution behavior.
+var context = {
+  foo: 'bar',
+  mypartial: {
+  	baz: 'qux'
+  }
+}
+var text = 'abc {{foo}} def {{>mypartial}} ghi';
+var partialText = '{{baz}}';
+var s = Mustache.to_html(text, context, {'mypartial': partialText});
+is(s, 'abc bar def qux ghi', 'Correct emulation of Mustache.js partial-name-in-context resolution.');
+
+// Now check to see that the Hogan resolution is unaffected.
+var t = Hogan2.compile(text);
+s = t.render(context, {'mypartial': partialText});
+is(s, 'abc bar def  ghi', 'Hogan behavior not changed by Mustache.js emulation.');
+
+// Check for sendFun behavior
+var buf = "";
+function send(s) {
+  buf += "-FOO " + s + " FOO-";
+}
+var s = Mustache.to_html(text, context, {'mypartial': partialText}, send);
+is(buf, '-FOO abc bar def qux ghi FOO-', 'Correct emulation of Mustache.js sendFun.');
+
+
+function is(got, expected, msg) {
+  if (got === expected) {
+    output("OK:   " + msg);
+    ++passed;
+  } else {
+    output("FAIL: " + msg);
+    output("Expected |" + expected + "|");
+    output("     Got |" + got + "|");
+    ++failed;
+  }
+}
+
+function complete() {
+  output("\nTests Complete");
+  output("--------------");
+  output("Passed: " + passed);
+  output("Failed: " + failed);
+  output("\n");
+}
+
+complete();

data/docs/build/node_modules/hogan.js/test/spec.js

@@ -0,0 +1,77 @@
+/*
+ *  Copyright 2011 Twitter, Inc.
+ *  Licensed under the Apache License, Version 2.0 (the "License");
+ *  you may not use this file except in compliance with the License.
+ *  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ *  Unless required by applicable law or agreed to in writing, software
+ *  distributed under the License is distributed on an "AS IS" BASIS,
+ *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ *  See the License for the specific language governing permissions and
+ *  limitations under the License.
+ */
+
+var Hogan = Hogan || require('../lib/hogan');
+var doc = this["document"];
+var fs = require('fs');
+
+var passed = 0;
+var failed = 0;
+
+if (!this["output"]) {
+  var output = function (string) {
+    return doc ? doc.write(string + '<br/>') : console.log(string);
+  };
+}
+
+function runTest(tests) {
+  tests.forEach(function(test) {
+    var partials = {};
+    for (var i in test.partials) {
+      partials[i] = Hogan.compile(test.partials[i]);
+    }
+    var t = Hogan.compile(test.template);
+
+    if (test.data.lambda) {
+      var func = (new Function ('return ' + test.data.lambda.js)());
+      test.data.lambda = function() { return func; };
+    }
+
+    var s = t.render(test.data, partials);
+    is(s, test.expected, test.name + ': ' + test.desc);
+  });
+}
+
+var testDir = './test/spec/specs';
+var files = fs.readdirSync(testDir)
+              .filter(function(f) { return f.indexOf('.json') > 0; })
+              .map(function(f) { return testDir + '/' + f});
+
+for (var i = 0; i < files.length; i++) {
+  var test = JSON.parse(fs.readFileSync(files[i]).toString());
+  runTest(test.tests);
+}
+
+function is(got, expected, msg) {
+  if (got === expected) {
+    output("OK:   " + msg);
+    ++passed;
+  } else {
+    output("FAIL: " + msg);
+    output("Expected |" + expected + "|");
+    output("     Got |" + got + "|");
+    ++failed;
+  }
+}
+
+function complete() {
+  output("\nTests Complete");
+  output("--------------");
+  output("Passed: " + passed);
+  output("Failed: " + failed);
+  output("\n");
+}
+
+complete();

data/docs/build/node_modules/hogan.js/test/spec/Changes

@@ -0,0 +1,31 @@
+2011-03-20: v1.1.2
+  Added tests for standalone tags at string boundaries.
+  Added tests for rendering lambda returns after delimiter changes.
+
+2011-03-20: v1.0.3
+  Added tests for standalone tags at string boundaries.
+  Added tests for rendering lambda returns after delimiter changes.
+
+2011-03-05: v1.1.1
+  Added tests for indented inline sections.
+  Added tests for Windows-style newlines.
+
+2011-03-05: v1.0.2
+  Added tests for indented inline sections.
+  Added tests for Windows-style newlines.
+
+2011-03-04: v1.1.0
+  Implicit iterators.
+    A single period (`.`) may now be used as a name in Interpolation tags,
+    which represents the top of stack (cast as a String).
+  Dotted names.
+    Names containing one or more periods should be resolved as chained
+    properties; naïvely, this is like nesting section tags, but with some
+    built-in scoping protections.
+
+2011-03-02: v1.0.1
+  Clarifying a point in the README about version compliance.
+  Adding high-level documentation to each spec file.
+
+2011-02-28: v1.0.0
+  Initial Release

data/docs/build/node_modules/hogan.js/test/spec/README.md

@@ -0,0 +1,65 @@
+The repository at https://github.com/mustache/spec is the formal standard for
+Mustache.  It defines both normal usage and edge-case behavior for libraries
+parsing the Mustache templating language (or a superset thereof).
+
+The specification is developed as a series of YAML files, under the `specs`
+directory.
+
+Versioning
+----------
+This specification is being [semantically versioned](http://semver.org).
+Roughly described, major version changes will always represent backwards
+incompatible changes, minor version changes will always represent new language
+features and will be backwards compatible, and patch ('tiny') version changes
+will always be bug fixes.  For the purposes of semantic versioning, the public
+API is the contents of the `specs` directory and the algorithm for testing
+against it.
+
+Mustache implementations SHOULD report the most recent version of the spec
+(major and minor version numbers).  If an implementation has support for any
+optional modules, they SHOULD indicate so with a remark attached to the
+version number (e.g. "vX.Y, including lambdas" or "v.X.Y+λ").  It is
+RECOMMENDED that implementations not supporting at least v1.0.0 of this spec
+refer to themselves as "Mustache-like", or "Mustache-inspired".
+
+Alternate Formats
+-----------------
+
+Since YAML is a reasonably complex format that not every language has good
+tools for working with, we also provide JSON versions of the specs on a
+best-effort basis.
+
+These should be identical to the YAML specifications, but if you find the need
+to regenerate them, they can be trivially rebuilt by invoking `rake build`.
+
+It is also worth noting that some specifications (notably, the lambda module)
+rely on YAML "tags" to denote special types of data (e.g. source code).  Since
+JSON offers no way to denote this, a special key ("`__tag__`") is injected
+with the name of the tag as its value.  See `TESTING.md` for more information
+about handling tagged data.
+
+Optional Modules
+----------------
+
+Specification files beginning with a tilde (`~`) describe optional modules.
+At present, the only module being described as optional is regarding support
+for lambdas.  As a guideline, a module may be a candidate for optionality
+when:
+
+  * It does not affect the core syntax of the language.
+  * It does not significantly affect the output of rendered templates.
+  * It concerns implementation language features or data types that are not
+    common to or core in every targeted language.
+  * The lack of support by an implementation does not diminish the usage of
+    Mustache in the target language.
+
+As an example, the lambda module is primarily concerned with the handling of a
+particular data type (code).  This is a type of data that may be difficult to
+support in some languages, and users of those languages will not see the lack
+as an 'inconsistency' between implementations.
+
+Support for specific pragmas or syntax extensions, however, are best managed
+outside this core specification, as adjunct specifications.
+
+Implementors are strongly encouraged to support any and all modules they are
+reasonably capable of supporting.

data/docs/build/node_modules/hogan.js/test/spec/Rakefile

@@ -0,0 +1,27 @@
+require 'json'
+require 'yaml'
+
+# Our custom YAML tags must retain their magic.
+%w[ code ].each do |tag|
+  YAML::add_builtin_type(tag) { |_,val| val.merge(:__tag__ => tag) }
+end
+
+desc 'Build all alternate versions of the specs.'
+multitask :build => [ 'build:json' ]
+
+namespace :build do
+  note = 'Do not edit this file; changes belong in the appropriate YAML file.'
+
+  desc 'Build JSON versions of the specs.'
+  task :json do
+    rm(Dir['specs/*.json'], :verbose => false)
+    Dir.glob('specs/*.yml').each do |filename|
+      json_file = filename.gsub('.yml', '.json')
+
+      File.open(json_file, 'w') do |file|
+        doc = YAML.load_file(filename)
+        file << doc.merge(:__ATTN__ => note).to_json()
+      end
+    end
+  end
+end

data/docs/build/node_modules/hogan.js/test/spec/TESTING.md

@@ -0,0 +1,46 @@
+Testing your Mustache implementation against this specification should be
+relatively simple.  If you have a readily available testing framework on your
+platform, your task may be even simpler.
+
+In general, the process for each `.yml` file is as follows:
+
+1. Use a YAML parser to load the file.
+
+2. For each test in the 'tests' array:
+
+  1. Ensure that each element of the 'partials' hash (if it exists) is
+     stored in a place where the interpreter will look for it.
+
+  2. If your implementation will not support lambdas, feel free to skip over
+     the optional '~lambdas.yml' file.
+
+  2.1. If your implementation will support lambdas, ensure that each member of
+       'data' tagged with '!code' is properly processed into a language-
+       specific lambda reference.
+
+      *   e.g. Given this YAML data hash:
+
+          `{ x: !code { ruby: 'proc { "x" }', perl: 'sub { "x" }' } }`
+
+          a Ruby-based Mustache implementation would process it such that it
+          was equivalent to this Ruby hash:
+
+          `{ 'x' => proc { "x" } }`
+
+      *   If your implementation language does not currently have lambda
+          examples in the spec, feel free to implement them and send a pull
+          request.
+
+      *   The JSON version of the spec represents these tagged values as a hash
+          with a '`__tag__`' key of 'code'.
+
+  3. Render the template (stored in the 'template' key) with the given 'data'
+     hash.
+
+  4. Compare the results of your rendering against the 'expected' value; any
+     differences should be reported, along with any useful debugging
+     information.
+
+     *  Of note, the 'desc' key contains a rough one-line description of the
+        behavior being tested -- this is most useful in conjunction with the
+        file name and test 'name'.

data/docs/build/node_modules/hogan.js/test/spec/specs/comments.json

@@ -0,0 +1 @@
+{"__ATTN__":"Do not edit this file; changes belong in the appropriate YAML file.","overview":"Comment tags represent content that should never appear in the resulting\noutput.\n\nThe tag's content may contain any substring (including newlines) EXCEPT the\nclosing delimiter.\n\nComment tags SHOULD be treated as standalone when appropriate.\n","tests":[{"name":"Inline","data":{},"expected":"1234567890","template":"12345{{! Comment Block! }}67890","desc":"Comment blocks should be removed from the template."},{"name":"Multiline","data":{},"expected":"1234567890\n","template":"12345{{!\n  This is a\n  multi-line comment...\n}}67890\n","desc":"Multiline comments should be permitted."},{"name":"Standalone","data":{},"expected":"Begin.\nEnd.\n","template":"Begin.\n{{! Comment Block! }}\nEnd.\n","desc":"All standalone comment lines should be removed."},{"name":"Indented Standalone","data":{},"expected":"Begin.\nEnd.\n","template":"Begin.\n  {{! Indented Comment Block! }}\nEnd.\n","desc":"All standalone comment lines should be removed."},{"name":"Standalone Line Endings","data":{},"expected":"|\r\n|","template":"|\r\n{{! Standalone Comment }}\r\n|","desc":"\"\\r\\n\" should be considered a newline for standalone tags."},{"name":"Standalone Without Previous Line","data":{},"expected":"!","template":"  {{! I'm Still Standalone }}\n!","desc":"Standalone tags should not require a newline to precede them."},{"name":"Standalone Without Newline","data":{},"expected":"!\n","template":"!\n  {{! I'm Still Standalone }}","desc":"Standalone tags should not require a newline to follow them."},{"name":"Multiline Standalone","data":{},"expected":"Begin.\nEnd.\n","template":"Begin.\n{{!\nSomething's going on here...\n}}\nEnd.\n","desc":"All standalone comment lines should be removed."},{"name":"Indented Multiline Standalone","data":{},"expected":"Begin.\nEnd.\n","template":"Begin.\n  {{!\n    Something's going on here...\n  }}\nEnd.\n","desc":"All standalone comment lines should be removed."},{"name":"Indented Inline","data":{},"expected":"  12 \n","template":"  12 {{! 34 }}\n","desc":"Inline comments should not strip whitespace"},{"name":"Surrounding Whitespace","data":{},"expected":"12345  67890","template":"12345 {{! Comment Block! }} 67890","desc":"Comment removal should preserve surrounding whitespace."}]}

data/docs/build/node_modules/hogan.js/test/spec/specs/comments.yml

@@ -0,0 +1,103 @@
+overview: |
+  Comment tags represent content that should never appear in the resulting
+  output.
+
+  The tag's content may contain any substring (including newlines) EXCEPT the
+  closing delimiter.
+
+  Comment tags SHOULD be treated as standalone when appropriate.
+tests:
+  - name: Inline
+    desc: Comment blocks should be removed from the template.
+    data: { }
+    template: '12345{{! Comment Block! }}67890'
+    expected: '1234567890'
+
+  - name: Multiline
+    desc: Multiline comments should be permitted.
+    data: { }
+    template: |
+      12345{{!
+        This is a
+        multi-line comment...
+      }}67890
+    expected: |
+      1234567890
+
+  - name: Standalone
+    desc: All standalone comment lines should be removed.
+    data: { }
+    template: |
+      Begin.
+      {{! Comment Block! }}
+      End.
+    expected: |
+      Begin.
+      End.
+
+  - name: Indented Standalone
+    desc: All standalone comment lines should be removed.
+    data: { }
+    template: |
+      Begin.
+        {{! Indented Comment Block! }}
+      End.
+    expected: |
+      Begin.
+      End.
+
+  - name: Standalone Line Endings
+    desc: '"\r\n" should be considered a newline for standalone tags.'
+    data: { }
+    template: "|\r\n{{! Standalone Comment }}\r\n|"
+    expected: "|\r\n|"
+
+  - name: Standalone Without Previous Line
+    desc: Standalone tags should not require a newline to precede them.
+    data: { }
+    template: "  {{! I'm Still Standalone }}\n!"
+    expected: "!"
+
+  - name: Standalone Without Newline
+    desc: Standalone tags should not require a newline to follow them.
+    data: { }
+    template: "!\n  {{! I'm Still Standalone }}"
+    expected: "!\n"
+
+  - name: Multiline Standalone
+    desc: All standalone comment lines should be removed.
+    data: { }
+    template: |
+      Begin.
+      {{!
+      Something's going on here...
+      }}
+      End.
+    expected: |
+      Begin.
+      End.
+
+  - name: Indented Multiline Standalone
+    desc: All standalone comment lines should be removed.
+    data: { }
+    template: |
+      Begin.
+        {{!
+          Something's going on here...
+        }}
+      End.
+    expected: |
+      Begin.
+      End.
+
+  - name: Indented Inline
+    desc: Inline comments should not strip whitespace
+    data: { }
+    template: "  12 {{! 34 }}\n"
+    expected: "  12 \n"
+
+  - name: Surrounding Whitespace
+    desc: Comment removal should preserve surrounding whitespace.
+    data: { }
+    template: '12345 {{! Comment Block! }} 67890'
+    expected: '12345  67890'