-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add some of the other cabal-fmt
refactorings?
#94
Comments
I would like to add support for importing fragments. |
I don't see any other pragmas that could be ported over: phadej/cabal-fmt#35 |
Yeah, I guess the fragments is the main one. This came up because we're thinking of using cabal-fmt's fragments, and I would otherwise suggest using cabal-gild :) |
I've tagged this as "help wanted". It would be nice for Gild to support importing fragments. I doubt I'll have the time to add that feature myself. |
@michaelpj @michaelpj Have you worked on this at all? If so, could you share your changes in a draft pr? |
I have not looked at this. |
No, I have not yet looked at this. I doubt I will anytime soon. My only thought about the implementation is that fragments importing other fragments is perhaps desirable but also could get stuck in a loop. Perhaps there should be a configurable maximum depth that defaults to something reasonable. |
cabal-fmt
has, as far as I know, two additional undocumented "refactorings" beyond expanding modules:I think both of these are quite nice features, it would be cool if
cabal-gild
had something similar.The text was updated successfully, but these errors were encountered: