[
https://issues.apache.org/jira/browse/SLING-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302384#comment-17302384
]
Carsten Ziegeler commented on SLING-10217:
------------------------------------------
This has been indirectly been discussed - the format should be valid json which
can be read by any parser. The support for comments in jsmin format is already
a stretch, but that is at least a well known extension of the format.
Multiline support is a different thing.
I guess the only use case we really have atm is repoinit and the feature model
solves that problem.
In addition "scripts" for repoinit is an array, so you can write each repoinit
statement as a separate script - they are applied in the order of the array.
Still a single statement might usually spawn several "lines", but that should
be much more readable
> Support multiline string values in cfg.json
> -------------------------------------------
>
> Key: SLING-10217
> URL: https://issues.apache.org/jira/browse/SLING-10217
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Configuration Factory 1.3.4
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently configurations of type {{.cfg.json}} only allow the JSON format
> defined by
> https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.configurator.html.
> For some very long values like {{scripts}} property for PID
> {{org.apache.sling.jcr.repoinit.RepositoryInitializer}} this makes the value
> very hard to read, as JSON does not support values spanning multiple lines.
> It would be nice if some line continuation character would be supported which
> allows to distribute a String value across multiple lines.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
