-
-
Notifications
You must be signed in to change notification settings - Fork 389
Make the Ormolu plugin respect .ormolu
fixity files when Ormolu ≥0.5.3.0
#3449
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
Conversation
aaffad3
to
95c1654
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
As for the reasons this is currently a draft, is there any particular conceptual reason why it would be difficult to better expose the functionality from upstream? Or is it just something that requires some boring grunt work?
It is just an API design question, e.g. involving how "coarsely-grained" mirroring the behavior of the executable via the Haskell API should be (see tweag/ormolu#969 and in particular tweag/ormolu#970 (review)). |
25800b6
to
32bbafe
Compare
Relevant upstream PR: tweag/ormolu#976 |
284838e
to
fe6f3f4
Compare
fe6f3f4
to
0c958da
Compare
.ormolu
fixity files.ormolu
fixity files when Ormolu ≥0.5.3.0
0c958da
to
6ee636f
Compare
when Ormolu ≥0.5.3.0
6ee636f
to
e9f9a49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, awesome!
Just want to discuss the SomeException
change, otherwise good to go!
Closes #3448; includes a regression test