You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2018/01/11 10:29:00 UTC

[jira] [Resolved] (SLING-7372) File system resource provider should support deep ValueMap access

     [ https://issues.apache.org/jira/browse/SLING-7372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Sedding resolved SLING-7372.
-----------------------------------
    Resolution: Fixed

Fixed in commit [c3adbae|https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-fsresource.git;a=commitdiff;h=c3adbae].

> File system resource provider should support deep ValueMap access
> -----------------------------------------------------------------
>
>                 Key: SLING-7372
>                 URL: https://issues.apache.org/jira/browse/SLING-7372
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: File System Resource Provider 2.1.8
>            Reporter: Julian Sedding
>            Assignee: Julian Sedding
>             Fix For: File System Resource Provider 2.1.10
>
>
> To make the file-system resource provider more useful in development scenarios, it should behave as similarly as possible to the JCR resource provider. Currently ValueMaps can only access properties of the current resource, but not using relative paths. Using relative paths is especially useful for prototyping HTL rendering scripts, because many properties can be accessed via {{properties['path/to/property']}} rather than requiring development of a model class.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)