Don't pass an empty {hash:{}} as the last arg to a template helper about blaze

[MiroHibler]

Would it make sense to simplify helpers to use either only positional or only keyword args? So either:

{{helper x y}}

Or

{{helper x=x y=y}}

The second seems more desirable as a single option, since with positional arguments you need to constantly be looking up the order, etc. Unfortunately all current code uses the first.

I'd do both for backward compatibility, get rid of hash and make the same for inclusion tags ({{> foo x y=y}}) and block tags ({{#foo x y=y}}).

[mitar]

This would potentially be backwards incompatible. But yes, this is really unneeded. Also, I think it is unneeded that data is stored inside hash ant not directly inside Spacebars.kw object.

[stubailo]

No reason I can imagine at all. We should 100% get rid of it.

[stubailo]

Would it make sense to simplify helpers to use either only positional or only keyword args? So either:

{{helper x y}}

Or

{{helper x=x y=y}}

The second seems more desirable as a single option, since with positional arguments you need to constantly be looking up the order, etc. Unfortunately all current code uses the first.

[mitar]

The question for me is just why we have hash property for data, why it is not simply an object which is an instance of something (Spacebars.kw) and this is it?

[stubailo]

I agree that helper and inclusion syntax should be consistent!

[filipenevola]

I'm closing this issue because it's too old.

If you think this issue is still relevant please open a new one.

Why? We need to pay attention to all the open items so we should keep opened only items where people are involved.