[CAUSEWAY-1388] Introduce @PropertyLayout(columnOrder=...) to make order of properties (when shown in tables) more predictable.

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.12.1
• Component/s: Applib (programming model)
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 22/Apr/16 12:21
• Updated: 29/Apr/22 15:44
• Resolved: 29/Apr/22 15:44

Description

At the moment it can be hard to predict, because the BS3Grid is traversed by type, eg:

    private void traverseCols(final Grid.Visitor visitor, final BS3Row bs3Row) {
        final BS3Grid.Visitor bs3Visitor = asBs3Visitor(visitor);
        final List<BS3RowContent> cols = bs3Row.getCols();
        for (BS3RowContent rowContent : Lists.newArrayList(cols)) {
            rowContent.setOwner(bs3Row);
            if(rowContent instanceof BS3Col) {
                final BS3Col bs3Col = (BS3Col) rowContent;
                bs3Visitor.preVisit(bs3Col);
                bs3Visitor.visit(bs3Col);
                traverseDomainObject(bs3Col, visitor);
                traverseTabGroups(bs3Col, visitor);
                traverseActions(bs3Col, visitor);
                traverseFieldSets(bs3Col, visitor);
                traverseCollections(bs3Col, visitor);
                traverseRows(bs3Col, visitor);
                bs3Visitor.postVisit(bs3Col);
            } else if (rowContent instanceof BS3ClearFix) {
                final BS3ClearFix bs3ClearFix = (BS3ClearFix) rowContent;
                bs3Visitor.visit(bs3ClearFix);
            } else {
                throw new IllegalStateException(
                        "Unrecognized implementation of BS3RowContent, " + rowContent);
            }
        }
    }

Instead, if it were traversed by element order, then the ordering of properties would be more predictable.