i propose a change how the i18n implementation interprets the keys in i18n JSON files. details are described in [1].
this change is fully backward compatible when the JSON files are just used as key-value map-like structure without any hierarchy - which is done by most users i assume. but if someone has used nested JSON files this change breaks with compatibility to the past releases. do you think anyone currently used these nested JSON structures not really well supported? can we break the behavior as described in the ticket (and document it properly)? making this feature configurable does no really help - it would always affect all i18n json files in the system. WDYT? stefan [1] https://issues.apache.org/jira/browse/SLING-6826
