bodigrim / cabal-add Goto Github PK

In line with the usual Cabal CLI, remove --cabal-file, add --project-file:

• If --project-file has been specified, parse it.
  • If --project file appears to be a Cabal file, go for it without complaints.
• If --project-file is not specified, look for cabal.project in the current folder.
• If cabal.project is not found, look for *.cabal in the current folder.

readProject provides us pretty much everything we need.

If a component target is not a common stanza then instead of resolving components on our own, we should use readBuildTargets from Cabal.

Since haskell/haskell-language-server#4360 adds a CodeAction which utilises cabal-add to add a dependency to a .cabal file, it would be much easier for HLS (especially when HLS does a Hackage release) if cabal-add was released to Hackage as well.

While we are not releasing right now, this issue aims to track a potential Hackage release.

cc @VenInf

The cabal-add tool looks up the cabal file by searching the current working directory.
I want to add the cabal-add tool to the hls and it would be very beneficial to have a way of specifying the path to the cabal file.
To my understanding, the --project-file is not related to this request (and also I failed to make this option work in this scenario).

Make --component optional: if a first positional argument can be parsed as a component target, do so. E. g., cabal-add tests bytestring should be equivalent to cabal-add --component tests bytestring.

This makes CLI more uniform with the usual Cabal conventions, which pass build targets positionally.