Apply the detected changes

dfithian commented 3 years ago

Fixes #6

Apply the proposed changes.

If you specify --apply, it will ask for confirmation after printing the results for every target. If you also specify --no-verify, it will apply the changes without confirmation. Haven't actually tested this part yet, but that's the way it should work.

One caveat here is that the pretty printing of the package description is different than the input file in a lot of cases, so it will mess up the .cabal file in question. Also I made it ignore package.yaml files. Maybe both of those things should be warnings.

Checklist:

[x] Test --apply
[x] Test --no-verify
[x] Add warnings for changing .cabal file and ignoring package.yaml
[x] If possible, instead of pretty printing the output, maybe do something like parsing the file halfway and modifying it in-place to cause as little churn as possible. Could do something like parsing test-suite <name> *> indentation *> build-depends <* end-indentation, overwriting the build-depends, and overwriting.
[x] Fix up the README

dfithian commented 2 years ago

As of the last commit, I tested it like this:

add transformers as a dependency to prune-juice.cabal
run stack run -- prune-juice --apply apply-no-verify --apply-strategy smart
~it correctly removed the dependency from the file, however it slightly changed the format ~ EDIT this is no longer true.

dfithian commented 2 years ago

@mirko-plowtech do you think this fixes your issue? You can test it out by running the following:

stack run -- prune-juice --apply

If you don't want it to prompt before applying, run

stack run -- prune-juice --no-verify

If it messes up your .cabal file, you can try running in "safe" mode with

stack run -- prune-juice --apply --apply-strategy safe

dfithian commented 2 years ago

I attempted this on my company's cabal files, which use common stanzas, and it didn't apply any of the changes. So I'll try to parse the common stanzas.

mirko-plowtech commented 2 years ago

@mirko-plowtech do you think this fixes your issue? You can test it out by running the following:
stack run -- prune-juice --apply
If you don't want it to prompt before applying, run
stack run -- prune-juice --no-verify
If it messes up your .cabal file, you can try running in "safe" mode with
stack run -- prune-juice --apply-strategy safe

Sorry the delay, I will try to test it this weekend =)

dfithian commented 2 years ago

I'm going to merge this so that some other contributions can be merged on top of it.

dfithian / prune-juice

Apply the detected changes #12