Problem
Our configuration dump starts in order:
|
pgrstSettings = (\(k, v) -> (k, v conf)) <$> |
|
[("client-error-verbosity", q . dumpClientErrorVerbosity . configClientErrorVerbosity) |
|
,("db-aggregates-enabled", T.toLower . show . configDbAggregates) |
|
,("db-anon-role", q . T.decodeUtf8 . fromMaybe "" . configDbAnonRole) |
|
,("db-channel", q . configDbChannel) |
Later at the end, it gets slightly out of order:
|
,("server-unix-socket-mode", q . T.pack . showSocketMode) |
|
,("admin-server-host", q . configAdminServerHost) |
|
,("admin-server-port", maybe "\"\"" show . configAdminServerPort) |
|
] |
Solution
I think users would like it to be in same order as listed in the docs. Nevertheless, I think it would be good to have it order to be consistent.
Problem
Our configuration dump starts in order:
postgrest/src/PostgREST/Config.hs
Lines 163 to 167 in ae7d4d2
Later at the end, it gets slightly out of order:
postgrest/src/PostgREST/Config.hs
Lines 202 to 205 in ae7d4d2
Solution
I think users would like it to be in same order as listed in the docs. Nevertheless, I think it would be good to have it order to be consistent.