Add for(integerVal) counting loops

[JaneOri]

Hey fam!

This adds integer count loops to output based on numbers.
Most frequently for me I've needed this for heavy visual builds.

	var template = stache("<div>{{#for(integerValue)}}[{{scope.index}}]{{/for}}</div>");
	var frag = template({
		integerValue: 3
	});
	// frag.firstChild.innerHTML === "[0][1][2]"

I queried about this years ago, wish I would have taken a look sooner since it was so easy to implement.

I understand if you decide against the feature, but I'd really like to have it and would be happy to discuss further if needed!

Hope you're all well!
//James

[justinbmeyer]

Do you think we should create a variable?

{{# for(ittr of this.integerValue) }}
  <li>{{scope.index}}: {{ ittr }}</li>
{{/ for }}

I sorta think access should be only through scope.index like: {{# for( this.integerValue ) }} {{scope.index}} {{/for}}.

[justinbmeyer]

On second thought, I think it's ok to make {{# for(ittr of this.integerValue) }} work. But I wouldn't show this as the main way of using it.

[justinbmeyer]

it seems there's some indentation inconsistency

[justinbmeyer]

We should probably clean up the signature docs, specifically around this part:

EXPRESSION {KeyLookup Expression|Call Expression}: An expression that typically returns a list like data structure. If the value of the EXPRESSION is an observable list (for example: can-define/list/list), the resulting HTML is updated when the list changes. When a change in the list happens, only the minimum amount of DOM element changes occur. The list itself can also change, and a difference will be performed, which also will perform a minimal set of updates.

I think we should make it more clear what happens if the expression evaluates to:

• An array-like structure (linking to canReflect.isListLike would be good here)
• An object-like (key-value) data structure
• A Number

[justinbmeyer]

Yeah, I think this is a great feature! I added notes for a few cleanup items. Thanks @James0x57 !

[JaneOri]

Hey Justin! I've Addressed each item

Here's what the updated expression part in the docs looks like locally now: