Ones that are all uppercase can conflict with system variables. Using
lower case or camelCase variables will ensure we will never conflict
with these predefined values.
This used to make a name like DATA.0.STR. Since bash doesn't like using
multi-dimensional arrays, we can shortcut things and just assume that
STR referes to the global variable here.
This closes issue #7
This lets the value returned from mustache-is-standalone get parsed
correctly. When this is a standalone template, the value returned looks
like "12 34" where each number is a position. Later, this is used in a
line that looks like `( $VALUE_RETURNED )`. When IFS does not contain a
space, this array is not built correctly.
Bug: Did not properly detect the length of an array in mustache-test
because I neglected to use `[@]` after the array name. This closes
issue #6.
Feature: Made {{ARRAY_NAME}} implode array values with commas.
Feature: Added an associative array demo script.
Blocks supporting standalone end tags was a matter of saying that this
could have been the beginning of the content.
Rewrote all partials to do in-bash string processing in order to add the
indent characters to all lines that have content.
Failing 28 out of 123 tests. At this point I have looked at all of the
tests and feel confident that they are because of features that are
intentionally not supported.
Pulled the block finding code into its own function to eliminate a
recursion problem.
Test failure count dropped because lambdas are supported and I just
needed to update the spec. Pull request mustache/spec#86 aims to add
bash support. Until then, the testing script will fall back to using
perl.
34 failing tests
* Trailing newline after a standalone tag can be "\r\n".
* Correctly returns the right number of characters to remove if the
standalone tag is at the end of the input (0 vs 1, didn't affect
behavior)
45 tests fail
