Unable to use {#} inside of {@select} due to lost context

[omnipenguin]

Example code:

Dust:

{@select key=lix_key}
  {@eq value="D"}
    {emails|js}
    {@contextDump key="current" to="console"/}
    {#emails.suggestedProfiles}
      {name}  
    {/emails.suggestedProfiles}
  {/eq}
...
{/select}

When trying to iterate using {#} within a {@select} block, the context appears to be lost. The iteration simply does not happen, even though the JSON object exists and is valid.
The object ({emails} in the example) when printed is perfectly fine and valid.
However when the current context is dumped within one of the {@eq} blocks, all that is outputted is:

JSON:

{
  "isSelect": true,
  "isResolved": true,
  "selectKey": "D"
}

This leads me to believe the current context is lost and thus the iteration doesn't happen. Removing the {@select} block makes everything work properly.

[jimmyhchan]

Please remove the internal link. It's meaningless on github.

Also please simplify example to highlight the issue

[omnipenguin]

Sorry about that. I updated my OP and cleaned up the code a bit. It's an extremely simplified version of the code I was working with.

[jimmyhchan]

This is actually the same as #9 and #42.

Possible fixes:

• use {#email}{#suggestedProfile}{name}{/suggestedProfile}{/email} which does not have dots and will not be affected by this bug.
  • change @select to push under the current context head the same way paritials parameters are currently being handled
• wait for the latest Dust core release that will change how paths are resolved.

[rragan]

The latest dust release is out there now. 2.0.0 and has the path change