Skip to content
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

stylish-haskell configuration file (EXPERIMENTAL, don't merge yet) #101

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

marcosh
Copy link
Contributor

@marcosh marcosh commented Oct 23, 2018

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 code

It would probably be nice to add them to the CI process, but I really have no idea how to add them to Nix

@epost
Copy link
Member

epost commented Oct 23, 2018

Thanks for picking this up Marco! I've been experimenting with these myself as well. Let's leave this PR as experimental just for a little bit, as I'd like to have a closer look at all of the settings and perhaps throw in some other formatters and possibly CI integration too.

@epost epost changed the title stylish-haskell configuration file stylish-haskell configuration file (EXPERIMENTAL, don't merge yet) Oct 23, 2018
@wires wires added the wip Work In Progress (not ready for merging) label Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
experimental wip Work In Progress (not ready for merging)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants