Rethink 'CliEnvSettings' and 'defaultCliEnvSettings' about iris HOT 3 CLOSED

@german1608 I believe no one is looking (or at least haven't written about this explicitly). So feel free to work on this 🙂

from iris.

Okay, I was thinking about the interface and here is the proposed solution:

• Remove the cliEnvSettingsRequiredTools :: [Tool cmd] field from the CliEnvSettings options
• Change the type of Tool to not have the cmd type parameter
• Implement a separate function need :: Monad ... => [Tool] -> m ()

So, instead of specifying a global list of tools, users can call the need function in the required commands:

app :: App ()
app = Iris.asksCliEnv Iris.cliEnvCmd >>= \case
    Download url -> do
        need ["curl"]
        runDownload URL
    Evaluate hs -> do
        need ["ghc", "cabal"]
        runEvaluate hs

from iris.

Is anyone working on this? I can take a look otherwise 😄

from iris.