stylish-haskell configuration file (EXPERIMENTAL, don't merge yet) #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
address partially #100
My proposal is to use https://hackage.haskell.org/package/hlint and https://hackage.haskell.org/package/stylish-haskell. Generally they should be installed locally and integrated with the development environment (for sublime-text, see https://packagecontrol.io/packages/SublimeLinter-hlint and https://packagecontrol.io/packages/StylishHaskell).
They are not tools which make you forget about styling, since they do not touch too much the structure of the code. If we want something more invasive, we could look at
hindent
, but I must say that I don't really like how it formats the codeIt would probably be nice to add them to the CI process, but I really have no idea how to add them to Nix