[
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394606#comment-15394606
]
Stefan Seifert commented on SLING-5886:
---------------------------------------
{quote}
I think we should not treat ValueMap as special and simply use
as(ValueMap.class) (it's not that much more complicated than asValueMap() but
removes two special methods). And in this case we could also describe what
happens if you do an as(ValueMap.class) without providing a name without
introducing a special case: it's simply taking the class name as the name.
{quote}
removed the special methods.
{quote}
One minor thing, a method named "asList" should return a List - a list has an
ordering, a collection does not. But I think ordering does not make sense, so
we should use a different name, getCollection maybe?
{quote}
renamed to asCollection.
> Sling Configuration - Initial Contribution
> ------------------------------------------
>
> Key: SLING-5886
> URL: https://issues.apache.org/jira/browse/SLING-5886
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
>
> as discussed in the mailing list (see [my post from april
> 2016|http://apache-sling.73963.n3.nabble.com/RT-Use-cases-for-content-specific-configurations-in-Sling-amp-Contribution-td4060813.html])
> i want to contribute the wcm.io Configuration parts that are not
> AEM-specific.
> the current features of wcm.io Configuration are described here:
> http://wcm.io/config/
> the main goal is to support "context-specific" configuration, that means
> configuration that is different for different content paths (e.g. sites,
> tenants).
> during the contribution some changes and refactorings are required/planned,
> e.g.:
> * remove some dependencies to wcm.io build environment, Guava and others
> * remove the "application" distinction currently part of wcm.io Configuration
> in favor or a more path-based distinction
> * refactor the user-faced configuration API to further simplify it and
> support OSGi R6-style annotation classed for typed configuration access
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
