[BUG] evaluation of object expression fails in nested each loops

[dharmax]

1. Describe your issue:
   Hello!
   i created a component with a nested loop:

 <li each="{i in state.items}" onclick="{()=>itemClick(i)}" class="{isPreselected(i)?'preselected':''}">
                <span each="{f in props.projection}">{i[f]}</span>
 </li>

An error was thrown, saying f was undefined.
Currently, i work around it, using a method:

<li each="{i in state.items}" onclick="{()=>itemClick(i)}" class="{isPreselected(i)?'preselected':''}">
                <span each="{f in props.projection}">{getField(i,f)}</span>
            </li>

and getField is simply returns i[f] and it works fine.

2. Can you reproduce the issue?

3. On which browser/OS does the issue appear?
   i checked only on Chrome

4. Which version of Riot does it affect?
   version 4.0.0.rc-14 (latest) and down.

[GianlucaGuarini]

Could you please create a simple demo demonstrating the issue?

[dharmax]

Sure. Is there a working skeletal riot 4 plnkr or something i could use?

[GianlucaGuarini]

@dharmax try with this https://plnkr.co/edit/TfeSSYTCY40QDYG7mOst?p=preview

[dharmax]

here it is: https://next.plnkr.co/edit/Zfq7eNUCCmYpvIbP

[GianlucaGuarini]

Ok I have found the issue, it's a compiler problem will fix it asap

[dharmax]

You're the best, pal :) btw, i also suggested returning the "virtual" tag. Also, would love to also see the "ref" special attribute too.

…

On Tue, May 21, 2019 at 3:33 PM Gianluca Guarini ***@***.***> wrote: Ok I have found the issue, it's a compiler problem will fix it asap — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2691?email_source=notifications&email_token=AAXZ5TTAZF5ADRO4K3ASCMDPWPTYJA5CNFSM4HN73YHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV3YFGA#issuecomment-494371480>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXZ5TW2A3L7C4PKLE7AHNLPWPTYJANCNFSM4HN73YHA> .

[GianlucaGuarini]

Fixed in riot@4.0.0-rc.17. The problem wasn't in the loop directives but in the compiler: computed MemberExpressions foo[bar] weren't properly scoped. Thanks to the new code managing these issues it's easy like a pie!