Thanks for the explanation.
This is quite a shame in my situation.
I am using dhall to generate a skeleton of infrastructure rules in an Openshift cluster. Developers would fill in a dhall form and automatically get a project (namespace) with correct defaults for quotas, …
I would like these forms to be as simple as possible as they will be consumed by many developers that know nothing about dhall. So ideally just records.
It would be really convenient to format these inputs automatically with dhall format
but I don’t believe user will like to see the current formatting rules applied on these simple records.
How can I possibly justify such arbitrary re-format in this context. For instance the following file:
{
, `limits.cpu` = "2"
, `requests.cpu` = "1"
, `limits.memory`= "2Gi"
}
is now
{ `limits.cpu` = "2", `requests.cpu` = "1", `limits.memory` = "2Gi" }
The user pulls back the file from the SCM later and wants to add a new constraint …
Is there any chance the decision gets revised in the future ?
Anyhow for the time being, I guess the best option is to avoid dhall format
on such trivial dhall forms.