Does the spec indictate how collections and other values should be rendered?

[dpeterson-git]

Consider a context object like this (in JSON notation):

{"A": [1, ["2", 3.0], {"D": 4}, 5.0, null, true, false, -314e-2]}

and a Mustache template like:

{{A}}

Most JavaScript-based implementations produce output like:

1,2,3,[object Object],5,,true,false,-3.14

However a prominent Java-based implementation produces output like:

[1, [2, 3.0], {D=4}, 5.0, null, true, false, -3.14]

Notable differences include:

1. Arrays are rendered with and without leading [ and trailing ] characters.
2. Items in the list/array are separated with , vs ,.
3. Objects are displayed as [object Object] vs {D=4}.
4. The null value displays as the empty string vs null.
5. Floating-point numbers are displayed as 5 vs 5.0.

Does the spec offer guidance on how these items should be rendered, or is this left up to implementations?

[jgonggrijp]

How to render collections is left implementation-defined:

spec/specs/interpolation.yml

Lines 23 to 24 in 83b221a

	Data should be coerced into a string (and escaped, if appropriate) before
	interpolation.

That being said, null should interpolate as the empty string:

spec/specs/interpolation.yml

Lines 104 to 120 in 83b221a

	- name: Basic Null Interpolation
	desc: Nulls should interpolate as the empty string.
	data: { cannot: null }
	template: "I ({{cannot}}) be seen!"
	expected: "I () be seen!"
	- name: Triple Mustache Null Interpolation
	desc: Nulls should interpolate as the empty string.
	data: { cannot: null }
	template: "I ({{{cannot}}}) be seen!"
	expected: "I () be seen!"
	- name: Ampersand Null Interpolation
	desc: Nulls should interpolate as the empty string.
	data: { cannot: null }
	template: "I ({{&cannot}}) be seen!"
	expected: "I () be seen!"

[dpeterson-git]

Understood. Thank you for the clarification.