You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have duplication in our archetypes to expose context value as model.
We need to expose context values as model directly to avoid the duplication.
I.e we need the ability to use {{groupId}} to reference ${groupId} without having to declare a model value.
Also we currently do not support dot notation as part of the mustache support. It would be a good time to re-visit that and implement support for dot notation in templates.
The dot notation would be useful in order to traverse the model. E.g. {{foo.bar}} refers to a map keyed as foo that contains a key bar.
Also, since this issue is about adding support for context, we should support context paths. This would mean supporting ~ and ...
The text was updated successfully, but these errors were encountered:
We currently have duplication in our archetypes to expose context value as model.
We need to expose context values as model directly to avoid the duplication.
E.g.
I.e we need the ability to use
{{groupId}}
to reference${groupId}
without having to declare a model value.Also we currently do not support dot notation as part of the mustache support. It would be a good time to re-visit that and implement support for dot notation in templates.
The dot notation would be useful in order to traverse the model. E.g.
{{foo.bar}}
refers to a map keyed asfoo
that contains a keybar
.Also, since this issue is about adding support for context, we should support context paths. This would mean supporting
~
and..
.The text was updated successfully, but these errors were encountered: