Handlebars: No Nested Paths about meteor HOT 6 CLOSED

it should be:

<template name="user">
<div class='navbar'>
<img src="logo.svg" />
<h1>Logged In {{firstName}}</h1>
</div>
</template>

Using user.firstname syntax would make it very hard for meteor do know what it is working on.

from meteor.

I get the same issue.

@callesg In the example above, calling <h1>Logged In {{user.firstName}}</h1> makes sense. The attribute name comes from the template function Template.navbarLoggedIn.user, hence {{user.firstName}} and not just {{firstName}}

from meteor.

@olivoil I get that it makes sense.
However (not saying this is not an issue in some way)

1. Having that would make it so that one template would be able to have more that one dependency. It may not be a problem by itself, but imagine all the complications that it would bring such as interfering dependencies.(AKA application bugs)
2. It basically only adds complexity such as(two ways to do one thing (the way i explained being one)), without any real benefits. Simplicity is nice.

Well that is my view of it.

from meteor.

Have you tried using {{this.firstName}} instead?

from meteor.

you can also use {{#with}} :

<template name="navbarLoggedIn">
<div class='navbar'>
<img src="logo.svg" />
{{#with user}}
  <h1>Logged In {{firstName}}</h1>
{{/with}}
</div>
</template>

from meteor.

Fixed on devel branch. You can now use nested paths on template properties, whether they are constants or getter functions.

from meteor.