[
https://issues.apache.org/jira/browse/SLING-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643127#comment-16643127
]
David Bosschaert commented on SLING-7990:
-----------------------------------------
Hi [~simone.tripodi], yes maybe something like this. For example have a test in
the build system that executes schema validator on some feature files to check
that they pass (or fail if expected) the validation.
> Define an initial version of the Feature Model JSON Shema
> ---------------------------------------------------------
>
> Key: SLING-7990
> URL: https://issues.apache.org/jira/browse/SLING-7990
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Affects Versions: Feature Model 0.1.2
> Reporter: Simone Tripodi
> Assignee: David Bosschaert
> Priority: Major
> Fix For: Feature Model 0.1.4
>
>
> As discussed in dev@ ML, there are multiple advantage of adopting such schema:
> * to have a formal and standard way to describe the Feature data structure
> in JSON model;
>
> * to provide an easy way to assist users on editing Feature json files in
> the right way inside IDEs, as shown in Eclipse[3] and IntelliJ[4];
> * to separate the input validation - it can be delegated by the Feature
> Analyzer - and the parser phases (which should just take care of transforming
> the JSON data to the Feature model)
> PS is coming
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
