You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2013/11/22 12:02:35 UTC

[jira] [Created] (ISIS-600) Change format of facet properties file, scope by member then facet

Dan Haywood created ISIS-600:
--------------------------------

             Summary: Change format of facet properties file, scope by member then facet
                 Key: ISIS-600
                 URL: https://issues.apache.org/jira/browse/ISIS-600
             Project: Isis
          Issue Type: Improvement
          Components: Core
    Affects Versions: core-1.3.0
            Reporter: Dan Haywood
            Assignee: Dan Haywood
            Priority: Minor
             Fix For: core-1.4.0


Although layout facets are most likely to be represented in json, they can also be loaded from a properties file.  Internally the json is converted to a bunch of properties, and it is the properties that are parsed and used to create facets.

Since this stuff was originally done for the memberOrder and memberOrderLayout facets, the properties file syntax is currently:

memberOrder.<memberName>.name=
memberOrder.<memberName>.sequence=

and

memberOrderLayout.columnSpans=3,4,0,5
memberOrderLayout.columnSpans.left=General,Detail

etc

This ticket is to invert this ordering, in preparation for other facets being added, and to distinguish member-level facets from class-level facets.  

eg:

member.<memberName>.memberOrder.name=
member.<memberName>.memberOrder.sequence=

and

memberOrderLayout.columnSpans=3,4,0,5
memberOrderLayout.columnSpans.left=General,Detail

The format of the JSON file is unchanged.



--
This message was sent by Atlassian JIRA
(v6.1#6144)