Skip to content

chore: config dump is slightly out of order #4769

@taimoorzaeem

Description

@taimoorzaeem

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions