tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (TAP5-2098) JSONObject should keep its properties in the order in which they were added
Date Tue, 30 Jul 2013 13:43:48 GMT

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

Jochen Kemnade reopened TAP5-2098:
----------------------------------


Could we please either make the JSONObject class extensible (i.e. non-final) or add a constructor
that takes a Map to back the JSONObject?
                
> 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
>            Priority: Minor
>              Labels: json, patch
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message