| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Fix Rakefile to add __tag__: code for ~lambda test data
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was broken when Ruby switched YAML engines from Syck to Psych
around Ruby 1.9.3. Syck was removed completely around version 2.0.
The code didn't fail, because Psych also implements the add_builtin_type
routine, but it does not recognize `!code` as a builtin type (because it
isn't; builtins look like !!str or !!map).
Instead, Psych requires a custom class to handle decoding the tagged
YAML item to Ruby.
And then, to get JSON to actually display the object, it is easiest to
just inherit from `Hash`.
|
| |\ \ \
| |/ /
| | | |
Pretty print JSON files, and terminate with newline
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Having the data all on one line makes it hard for implementations that
rely on the JSON format to locate the source of a failure.
Text files that don't end with a newline can be troublesome or
unacceptable in some contexts.
The only down side is a bit of merging hassle for existing pull
requests. But that happens anyways, and of course the YAML file is
authoritative so JSON conflicts can be ignored in practice.
|
| |\ \
| | |
| | | |
Fix TESTING.md Markdown list syntax; no content changes
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The present indentation isn't valid Markdown, and breaks the display
when viewing the rendered file, as on Github. Please compare:
- Old: https://github.com/mustache/spec/blob/f75ffbf0a90e6ccecb11df58cdb4cc400ac2919d/TESTING.md
- Numbering goes 1, 2, 3 (wrong), 4 (wrong), 2.1 (out-dented, not part
of the list), 3, 4.
- Bulleted list under section 2.1 is entirely preformatted, rather
than rendered as the intended list items
- New: https://github.com/softmoth/mustache-spec/blob/format-testing-doc/TESTING.md
This patch moves what was "item" 2.1 back under item 2 without an extra
list item. Unfortunately, Markdown doesn't handle this particular
structure elegantly as far as I know.
It also switches to backtick quotes for all literals.
|
| |\ \ \
| | | |
| | | | |
~lambdas: Add Raku language tests (formerly Perl 6)
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| | |
Fix Variable test in sections.yml
|
| | | | |
|
| |/ / |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The behavior of "context stacks" is not explained very clearly in the
documentation outside the spec, but the following text from
mustache(5) (http://mustache.github.io/mustache.5.html) is pretty
clear:
> A {{name}} tag in a basic template will try to find the name key in
> the current context. If there is no name key, the parent contexts
> will be checked recursively. If the top context is reached and the
> name key is still not found, nothing will be rendered.
In particular, when the documentation of section mentions that
> When the value is a non-empty list [..]. The context of the block
> will be set to the current item for each iteration.
or
> When the value is non-false but not a list, it will be used as the
> context for a single rendering of the block.
it should be understood that the new context becomes the "current
context", and that the previous context becomes a "parent context",
and its binding are still available.
The new tests check that these properties hold, in particular for
sections on non-object non-false values, where this was not previously
tested in the spec.
|
| |\ \
| | |
| | | |
Refresh the JSON specs
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| | |
On my system (yaml gem version 0.1.0), `foo.merge(bar)` will include the
keys of `foo` before the keys of `bar`, so the previous Rakebuild
definition would include the ATTN warning *after* the test data in the
rendered JSON files.
|
| |\ \
| | |
| | | |
Allow iterating over implicit iterators.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Implicit iterators should be treated just like
explicit tags, i.e. they should work for iterating
over nested arrays.
{{#items}}
{{#.}}
{{.}}
{{/.}}
{{/items}}
See mustache/mustache#177
|
| |\ \ \
| |/ /
|/| | |
Add lambda spec for Common Lisp
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| |/
|/| |
Add a test that dotted name resolution should make forward-only progress
|
| | | |
|
| |/
|
|
|
| |
This test case tests that successive portions of dotted names should be
resolved against former resolutions (i.e. forward-only progress).
|
| | |
|
| | |
|
| |\ |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
Changes
|
| | | |
|
| | | |
|
| |\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
Changes
specs/inverted.json
specs/sections.json
|
| | | |
|
| | | |
|
| |\ \
| |/
| |
| |
| | |
Conflicts:
Changes
|
| | | |
|
| |\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
specs/comments.json
specs/inverted.json
specs/sections.json
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
| |
| |
| |
| | |
Conflicts:
specs/inverted.yml
specs/sections.yml
|
| | | |
|
