Fields are not in the order of the definition

mikeplus64 / aeson-flowtyped

Moved to https://gitlab.com/transportengineering/aeson-flowtyped

BSD 3-Clause "New" or "Revised" License

6 stars 2 forks source link

Fields are not in the order of the definition #2

Open mgsloan opened 6 years ago

mgsloan commented 6 years ago

Often the order of the haskell fields is something sensible and nice to read. While I realize that aeson and JS freely reorder the keys of an object, it would be good to preserve the order of the haskell definitions.

mikeplus64 commented 6 years ago

Not against this, but I don't think it's worth worrying about. If aeson-flowtyped used TH instead it could probably preserve comments on specific fields as well.

mgsloan commented 6 years ago

Unfortunately, TH doesn't have access to that currently. Would be nice if it did, though!