tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2098) JSONObject should keep its properties in the order in which they were added
Date Mon, 04 Nov 2013 21:30:19 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813298#comment-13813298
] 

ASF subversion and git services commented on TAP5-2098:
-------------------------------------------------------

Commit dd6fa7bc617e197d4298b1b3a8adb0a70b8e6933 in branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=dd6fa7b ]

TAP5-2098: Maintain JSONObject keys & values in the order they were added


> JSONObject should keep its properties in the order in which they were added
> ---------------------------------------------------------------------------
>
>                 Key: TAP5-2098
>                 URL: https://issues.apache.org/jira/browse/TAP5-2098
>             Project: Tapestry 5
>          Issue Type: Wish
>          Components: tapestry-json
>    Affects Versions: 5.3, 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: json, patch
>             Fix For: 5.4
>
>
> While JSON objects are unordered according to the specification, it would be nice if
Tapestry's implementation kept its properties in the order of their insertion. That way, it
could be used for pretty-printing more easily.



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

Mime
View raw message