You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Anatole Tresch (JIRA)" <ji...@apache.org> on 2018/10/23 16:33:00 UTC
[jira] [Assigned] (TAMAYA-355) Revise mapping of xml, json and yaml
configurations to honor lists
[ https://issues.apache.org/jira/browse/TAMAYA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anatole Tresch reassigned TAMAYA-355:
-------------------------------------
Assignee: Anatole Tresch
> Revise mapping of xml, json and yaml configurations to honor lists
> ------------------------------------------------------------------
>
> Key: TAMAYA-355
> URL: https://issues.apache.org/jira/browse/TAMAYA-355
> Project: Tamaya
> Issue Type: Improvement
> Components: Core, Extensions
> Affects Versions: 0.3-incubating
> Reporter: Anatole Tresch
> Assignee: Anatole Tresch
> Priority: Blocker
> Fix For: 0.4-incubating
>
>
> Given the following config:
> {{<config>}}
> {{ <a>}}
> {{ <b>23</b>}}
> {{ </a>}}
> {{ <a>}}
> {{ <b>15</b>}}
> {{ </a>}}
> {{</config>}}
> The current mapping (in _core_, and the _format_ related modules) results in a.b=15, which is invalid, because it actually looses information.
> This is basically similar for other formats. This change defines that list entries are mapped to arrays as follows:
> {{a[0].b=23}}
> {{a[1].b=15}}
> This syntax does not loose information and is simple enough to reestablish access logic such as
> {{List<Map<String,String>> as = configuration.query(ListQuery.of("a"));}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)