tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-2098) JSONObject should keep its properties in the order in which they were added
Date Mon, 04 Nov 2013 21:30:18 GMT

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

Howard M. Lewis Ship closed TAP5-2098.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4

> 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