-
-
Notifications
You must be signed in to change notification settings - Fork 389
Brittany is not initialised with stack default extensions #665
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
Comments
Is |
This was simply so you can enable/disable easily - it's a comment until you remove the whitespace |
The point being that since the extension was inactive (the pragma was commented out), the bug arose |
This comment has been minimized.
This comment has been minimized.
Sorry, I have misread the issue. So the problem is that Brittany does not recognize the extension in |
@Ailrun I believe this to be the case. I'm not aware whether hls picks up the config in package.yaml. If so, this might not be such a hard enhancement. I can always take a look if someone is willing to point me somewhere in the code :) |
Afaik this should be closed by #1362, @santiweight could you confirm brittany honours stack default extensions? |
I am unsure whether this is a feature request or a bug...
VS Code - haskell extension
Bug repro
https://github.com/santiweight/hls-bug-brittany
See the diff for the most recent commit
Contents of
hie.yaml
:Steps to reproduce
Have a syntactic extension (e.g. PatternSynonyms) in package.yaml's default extensions and then pretty print using Brittany.
Expected behaviour
Pretty printing should occur
Actual behaviour
Error prints:
The text was updated successfully, but these errors were encountered: