[ 
https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229753#comment-14229753
 ] 

ASF GitHub Bot commented on SLING-4212:
---------------------------------------

GitHub user santiagozky opened a pull request:

    https://github.com/apache/sling/pull/51

    Resource path list support

    SLING-4212

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/santiagozky/sling resourcePathMultiple

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/51.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #51
    
----
commit be0ccd651ddea99c5be8e76a96c1252e82ce0e5d
Author: santiago garcia pimentel <santiago.pimen...@netcentric.biz>
Date:   2014-12-01T12:34:58Z

    make resourcePath injector accept multiple paths from valuemap

commit 5fdc9b855b15cf7db7816c0ad5804ee28e496fe0
Author: santiago garcia pimentel <santiago.pimen...@netcentric.biz>
Date:   2014-12-01T12:43:16Z

    fix formating

----


> Sling Models: Allow multiple values from ValueMap in the resource-path 
> injector
> -------------------------------------------------------------------------------
>
>                 Key: SLING-4212
>                 URL: https://issues.apache.org/jira/browse/SLING-4212
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: santiago garcĂ­a pimentel
>
> The current implementation of the resource-path injector does not support 
> multiple values. I think it could be useful to inject a list of paths from 
> the valuemap.
>  I have created a small patch to allow this. Right now it only allows them 
> from the value map since I didn't want to change the API without consulting 
> you first. I you agree I can do this change as well. I also added a test case 
> for it.
> If there anything I can do to improve this patch, please let me know.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to