Sander Ginn created ISIS-1029:
---------------------------------

             Summary: Hidden{where} in layout is not honored by table 
representations
                 Key: ISIS-1029
                 URL: https://issues.apache.org/jira/browse/ISIS-1029
             Project: Isis
          Issue Type: Bug
          Components: Viewer: Wicket
    Affects Versions: viewer-wicket-1.8.0
            Reporter: Sander Ginn
            Assignee: Dan Haywood


On removal of all annotations and defining hidden property in the respecting 
layout json files, these definitions are not honored in table representations. 

Below is an example of how I defined the layout:

{code}
{
      "span": 2,
      "memberGroups": {
        "Dates": {
          "members": {
            "startDate": {
              "disabled": {},
              "hidden": {
                "where": "EVERYWHERE"
              },
              "typicalLength": {
                "value": 12
              }
            },
            "endDate": {
              "actions": {
                "changeDates": {}
              },
              "disabled": {},
              "hidden": {
                "where": "EVERYWHERE"
              },
              "typicalLength": {
                "value": 12
              }
            },
            "tenancyStartDate": {
              "disabled": {},
              "hidden": {
                "where": "NOWHERE"
              },
              "typicalLength": {
                "value": 12
              }
            },
            "tenancyEndDate": {
              "disabled": {},
              "hidden": {
                "where": "NOWHERE"
              },
              "typicalLength": {
                "value": 12
              }
            },
            "tenancyDuration": {
              "actions": {
                "changeTenancyDates": {}
              },
              "disabled": {},
              "typicalLength": {
                "value": 25
              }
            }
          }
        }
      }
    }
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to