-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[etlas] Migrate to hpack #642
Comments
Another interesting idea would be if I mean, no cabal file would be generated in the root of the project, or at least unless specified. This would lead to less confusions in my opinion. "Why do you have two project config files?" |
That was intended above - I was probably not clear. The idea is to eventually move to a |
Maybe we can consider the use of dhall instead (directly or using dhall-to-cabal), as commented in #704. |
I like dhall, but sometimes it looks really verbose. We should abstract stuff from it. |
Well i think that finally dhall would be the chosen format (see typelead/etlas#66) so it seems we can close this one. |
https://github.com/sol/hpack is a wonderful tool to convert yaml files into Cabal files. The syntax for Cabal files can be adhoc at times so having something structured and standardized like yaml seems like a great fit. It seems like a great idea for Etlas to make a yaml-like format the default.
The text was updated successfully, but these errors were encountered: