Closed mx00s closed 4 years ago
One question I have is whether the files which aren't suffixed with .dhall
are truly necessary. My understanding is that they were introduced into the Prelude strictly as a backwards compatibility measure. I'd prefer to eliminate this source of noise if it isn't actually best-practice.
No, they're not necessary. That's a good point that it was done that way for backwards compatibility; I hadn't considered that. dhall-kubernetes
consistently uses the .dhall
extension.
I will remove the unnecessary files.
The latest commit removes those unnecessary files.
The top-level package.dhall file gives users a single entrypoint to access expressions in this repo.
There were some name and structuring changes which affect the exposed top-level expressions. For example, all the functions in
./rendering
were moved totoJSON.dhall
files in the appropriate./GitLab/<type>/
directories. More concretely,./rendering/Top.dhall
became(./package.dhall).Top.toJSON
.This resolves #1.