Expressions evaluation unclear/undocumented

[Gamadril]

Help us to manage our issues by answering the following:

1. Describe your issue:
   It's totally unclear for me how expressions inside { } are evaluated. The documentation says:

All template expressions are “just javascript™️”: <pre>{ JSON.stringify(props) }</pre>

the example above works, but accessing other global variables not. Currently I cannot find a way to get { i18next.t('settings') } evaluated. In the generated code i18next is prefixed with "scope." So why "JSON.stringify" not? Isn't it also globally defined in window?

It would be easier for me as a developer to know in which cases "scope." is prefixed and in which not. And there should be a way (using special syntax maybe) to tell the compiler not to prefix the expressions (Feature Request).

2. Can you reproduce the issue?

https://plnkr.co/edit/IQusfuupsQZueucRqjL8?p=preview

3. On which browser/OS does the issue appear?
   All

4. Which version of Riot does it affect?
   v4.5.0

5. How would you tag this issue?

• Question
• Bug
• Discussion
• Feature request
• Tip
• Enhancement
• Performance

[GianlucaGuarini]

The proper way to render custom global variables in this case would be window.i18next.t('key'). While JSON is a known window/node global object i18next is not and that's why the Riot.js compiler doesn't know where to get this value. I will work on a patch ASAP. Thank you

[Gamadril]

Actually "window." was the first thing I've tried, but it is still prefixed:

[GianlucaGuarini]

@Gamadril that's the bug I will need to fix 😄 in the mean time something like this should be a bit cleaner and more elegant anyway

import i18next from 'i18next'

export default {
   i18next
}

[Gamadril]

Thanks for the hint, I can live for now with the workaround 😄

[GianlucaGuarini]

Fixed in Riot.js@4.5.1 thank you for reporting it