Open theGhostJW opened 6 years ago
Where would I start fixing this issue?
I would start with having a minimal example where this behaviour can be reproduced.
Then, I would compare the output with an actual invocation of hlint
, make sure this is not a bug upstream. Then, in the plugin ApplyRefact
, iirc, you can compare the invocation of the linting command, lintCmd
. Maybe there you already would need to specify the active Language Extensions? In particular, the function invocation of parseModuleEx
in runLintCmd
seems promising for a first investigation.
If you fix it, please add a validating test-case!
package.yaml
.hlint.yaml
hlint will run from the command line with no hints for a file that includes something like:
but atom (running haskell-hie extension) returns hlint warning (description
Parse error ...
).The workaround is to add
{-# LANGUAGE QuasiQuotes #-}
to the top of each file that utilises QuasiQuotes.