You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/06/22 05:29:00 UTC

[jira] [Resolved] (SLING-10494) Configuration API should have a way to allow empty configurations

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

Carsten Ziegeler resolved SLING-10494.
--------------------------------------
    Resolution: Fixed

Implemented in https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/commit/c1ed74c71dccbf12c78a3a13f7f788f3cac4b807

allow-additional-properties can now be specified on a configuration to allow for this use case.

Added an additional region and internal-property-names configuration as well, allowing to mark a configuration as internal and mark certain properties as internal.

> Configuration API should have a way to allow empty configurations
> -----------------------------------------------------------------
>
>                 Key: SLING-10494
>                 URL: https://issues.apache.org/jira/browse/SLING-10494
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: Feature Model API Regions Extension 1.3.0
>            Reporter: Karl Pauls
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model API Regions Extension 1.3.2
>
>
> The way the Configuration API currently handles configurations (and factory configurations) is that an empty entry means don't allow. In other words, listing an empty configuration (factory) is the same as marking it as internal-configuration(-factory). 
> That makes sense in as far as that makes it nicer to be able to specify configurations that are not allowed inline with the other configurations - however, it misses a case where it is now impossible to allow an empty configuration. 
> That could be problematic as sometimes, empty configurations are used to configure e.g. services - that use case would at a minimum now not show up in the Configuration API as one would be forced not to mention the configuration at all in order to allow somebody to still be able to create an empty configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)