[
https://issues.apache.org/jira/browse/SLING-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-10652.
-------------------------------------
Assignee: Konrad Windszus (was: Radu Cotescu)
Resolution: Fixed
Fixed in
https://github.com/apache/sling-site/commit/ac12de1fa98bd50958d6d0e606e7cc35f05f99aa.
> Add a type coercion table to the HTL Engine documentation
> ---------------------------------------------------------
>
> Key: SLING-10652
> URL: https://issues.apache.org/jira/browse/SLING-10652
> Project: Sling
> Issue Type: Improvement
> Components: Documentation, Scripting
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The HTL specification only refers to programming language agnostic types like
> numeric, string or date. As the HTL Engine in Sling (or rather the use
> providers) map the native types in either Java or JavaScript accordingly
> there should be some information which native type can be translated into
> which HTL type (and how this is done, in case this is not obvious). This is
> crucial as e.g. in the context of SLING-10651 more types are now supported.
> The following types are mentioned in the HTL spec
> # Boolean
> # String
> # Number
> # Date
> # Collection
> # Map
> # Enum
> It would be helpful to know how Java types are converted into those.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
