Empty nested variables breaking templates when used inside components

• Maizzle Version: 4.0.0
• Node.js Version: 16.5.3

Hi,

It’d be really handy if we were able to build templates locally that include nested variables e.g. page.myVariable.myNestedVariable. Currently we’re having to insert these into our maizzle config when developing locally, e.g:

const config = {
  ...
  myVariable: {
  }
}

If maizzle serve used lodash/get (or similar) for getting template variables that would save us a lot of hassle. Alternatively, if maizzle serve supported optional chaining that would also help, but even on new versions of node optional chaining doesn’t seem to do anything, the templates still break.

Thanks!

[jebax]

I just tested in a fresh new project and simply replaced the contents of promotional.html with this:

<extends src="src/layouts/main.html">
  <block name="template">
    {{ page.foo?.bar || 'default' }}
  </block>
</extends>

Could be related to outdated dependencies / your yarn problem perhaps?

Tried again and it worked, I think it was due to me not deleting node_modules before reinstalling like you say! Don’t think it’s related to that other issue though.

Thanks for your time anyway, I appreciate it

[jebax]

Yeah, it’s not intentional, just the way posthtml-modules (what we use for components) works.

A way around it is to use a fallback of some kind, or optional chaining:

<!-- v-fill.html -->
<content></content>

{{ page.x?.y.z }}

Ah ok, thanks for the info!