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 2022/01/07 06:51:00 UTC

[jira] [Resolved] (SLING-11047) JSON schema should use start-order

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

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

Fixed in https://github.com/apache/sling-org-apache-sling-feature/commit/4cfeb7a210cdc29f8e611f784586fb4ca5ded2a7

(The change is not breaking anything as any property is allowed by schema including start-order)

> JSON schema should use start-order
> ----------------------------------
>
>                 Key: SLING-11047
>                 URL: https://issues.apache.org/jira/browse/SLING-11047
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: Feature Model 1.2.28
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model 1.2.30
>
>
> The JSON schema for the feature model is wrongly defining "start-level" instead of start-order.
> While this doesn't create problems, it is demonstrating the wrong property name



--
This message was sent by Atlassian Jira
(v8.20.1#820001)