[
https://issues.apache.org/jira/browse/TAP5-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship resolved TAP5-2098.
----------------------------------------
Resolution: Invalid
I'm not sure what it has to do with pretty printing, but we're not going to add
new functionality on top of JSON's rather precise specification. Doing so will
cause more harm, as people in the Tapestry world will expect that functionality
even when receiving JSON from other sources.
> 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
