Template expression are evaluated only in the last attribute

[kosek]

Hi,

when more attributes contain template expression, e.g.:

<template >
      <option value="{Id}" title="{Title}" data-test="{1+2}">{Value}</option>
</template>

Then template only in the last attribute is being evaluated producing the following HTML:

<template >
      <option value="{Id}" title="{Title}" data-test="3">Value from XML</option>
</template>

But {Id} and {Title} should be also populated by data coming from the instance, but they keep untouched and unprocessed.

[kosek]

Actually this happens only on complex page, simple usage works and template expressions are evaluated in all attributes. I will try to isolate test case that shows error.

What happens in JavaScript console is that for each expression that is not evaluated the following error is shown no inscope context for expr ...

[DrRataplan]

Hey @kosek,

Long time no talk! The template expressions should take their context from whatever is inscope there. So the nearest @ref in the inclusive ancestry. A repro would be amazing, especially if it only occurs in more complex pages. Feel free to just give a more complex page, if that's the only way to repro it.

If you are using a select it is a bit more iffy though. This code is quite old and still does template expansion manually (https://github.com/Jinntec/Fore/blob/dev/src/ui/fx-control.js#L689), instead of using the centralized template expansion. Should not be too difficult to refactor, but your error message makes me think this is not actually the culprit.

Any chance for a more minimal repro?

Kind regards,

Martin

[JoernT]

@kosek please provide a complete example