You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as _swaggerPaths is a HashMap, not only the order is different from what is declared (e.g. in servant API type), it's arbitrary. For machine reading, it's ok; but swagger-ui suffer from this:
I could work on this, if we agree on solution. Either we could change HashMap FilePath PathItem to Vector (FilePath, PathItem), maybe wrapped in newtype.
EDIT; That won't be easy to fix, as the paths is an object in JSON representation, yet that could be worked around in >=aeson-0.10 by using toEncoding (so one can specify an order of output!)
The text was updated successfully, but these errors were encountered:
--| A @'HashMap'@ with an explicit ordering of the keys.dataOrdHashMapkv=OrdHashMap{ordHashMapKeys::Vectork--^ Explicit ordering of the keys.
, ordHashMapMap::HashMapkv--^ The mapping.}
Also, we can replace all/most of the HashMaps used in the data model.
For instance, this ordering might also be useful for Schema's properties.
as
_swaggerPaths
is aHashMap
, not only the order is different from what is declared (e.g. inservant
API type), it's arbitrary. For machine reading, it's ok; but swagger-ui suffer from this:I could work on this, if we agree on solution. Either we could change
HashMap FilePath PathItem
toVector (FilePath, PathItem)
, maybe wrapped innewtype
.EDIT; That won't be easy to fix, as the
paths
is an object in JSON representation, yet that could be worked around in>=aeson-0.10
by usingtoEncoding
(so one can specify an order of output!)The text was updated successfully, but these errors were encountered: