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
I think I understood the structure of these examples, but one thing that comes up often in practice: versioned configuration.
That is, the program in question changes the types of some fields, removes some fields, adds some fields …
How would I write a dhall config that can handle this? Where the user should (if possible) be able to import a dhall file that corresponds to the version of the program one wants to generate the config for, and dhall will typecheck for that version number.
Of course on the dhall side there should be as little duplication as possible.
The text was updated successfully, but these errors were encountered:
I think I understood the structure of these examples, but one thing that comes up often in practice: versioned configuration.
That is, the program in question changes the types of some fields, removes some fields, adds some fields …
How would I write a dhall config that can handle this? Where the user should (if possible) be able to import a dhall file that corresponds to the version of the program one wants to generate the config for, and dhall will typecheck for that version number.
Of course on the dhall side there should be as little duplication as possible.
The text was updated successfully, but these errors were encountered: