{-# LANGUAGE RecordWildCards #-}

-- | cabal-install CLI command: haddock
module Distribution.Client.CmdHaddock
  ( -- * The @haddock@ CLI and action
    haddockCommand
  , haddockAction
  , ClientHaddockFlags (..)

    -- * Internals exposed for testing
  , selectPackageTargets
  , selectComponentTarget
  ) where

import Distribution.Client.Compat.Prelude
import System.Directory (makeAbsolute)
import Prelude ()

import Distribution.Client.CmdErrorMessages
import Distribution.Client.NixStyleOptions
  ( NixStyleFlags (..)
  , defaultNixStyleFlags
  , nixStyleOptions
  )
import Distribution.Client.ProjectConfig.Types
  ( PackageConfig (..)
  , ProjectConfig (..)
  )
import Distribution.Client.ProjectOrchestration
import Distribution.Client.ProjectPlanning
  ( ElaboratedSharedConfig (..)
  )
import Distribution.Client.Setup
  ( CommonSetupFlags (..)
  , ConfigFlags (..)
  , GlobalFlags
  , InstallFlags (..)
  )
import Distribution.Client.TargetProblem
  ( TargetProblem (..)
  , TargetProblem'
  )
import Distribution.Simple.Command
  ( CommandUI (..)
  , OptionField
  , ShowOrParseArgs
  , option
  , usageAlternatives
  )
import Distribution.Simple.Flag (Flag (..))
import Distribution.Simple.Program.Builtin
  ( haddockProgram
  )
import Distribution.Simple.Program.Db
  ( addKnownProgram
  , reconfigurePrograms
  )
import Distribution.Simple.Setup
  ( HaddockFlags (..)
  , fromFlagOrDefault
  , trueArg
  )
import Distribution.Simple.Utils
  ( dieWithException
  , notice
  , wrapText
  )
import Distribution.Verbosity
  ( normal
  )

import Distribution.Client.Errors
import qualified System.Exit (exitSuccess)

newtype ClientHaddockFlags = ClientHaddockFlags {openInBrowser :: Flag Bool}

haddockCommand :: CommandUI (NixStyleFlags ClientHaddockFlags)
haddockCommand =
  CommandUI
    { commandName = "v2-haddock"
    , commandSynopsis = "Build Haddock documentation."
    , commandUsage = usageAlternatives "v2-haddock" ["[FLAGS] TARGET"]
    , commandDescription = Just $ \_ ->
        wrapText $
          "Build Haddock documentation for the specified packages within the "
            ++ "project.\n\n"
            ++ "Any package in the project can be specified. If no package is "
            ++ "specified, the default is to build the documentation for the package "
            ++ "in the current directory. The default behaviour is to build "
            ++ "documentation for the exposed modules of the library component (if "
            ++ "any). This can be changed with the '--internal', '--executables', "
            ++ "'--tests', '--benchmarks' or '--all' flags.\n\n"
            ++ "Currently, documentation for dependencies is NOT built. This "
            ++ "behavior may change in future.\n\n"
            ++ "Additional configuration flags can be specified on the command line "
            ++ "and these extend the project configuration from the 'cabal.project', "
            ++ "'cabal.project.local' and other files."
    , commandNotes = Just $ \pname ->
        "Examples:\n"
          ++ "  "
          ++ pname
          ++ " v2-haddock pkgname"
          ++ "    Build documentation for the package named pkgname\n"
    , commandOptions = nixStyleOptions haddockOptions
    , commandDefaultFlags = defaultNixStyleFlags (ClientHaddockFlags (Flag False))
    }

-- TODO: [nice to have] support haddock on specific components, not just
-- whole packages and the silly --executables etc modifiers.

haddockOptions :: ShowOrParseArgs -> [OptionField ClientHaddockFlags]
haddockOptions _ =
  [ option
      []
      ["open"]
      "Open generated documentation in the browser"
      openInBrowser
      (\v f -> f{openInBrowser = v})
      trueArg
  ]

mkConfigAbsolute :: ProjectConfig -> IO ProjectConfig
mkConfigAbsolute relConfig = do
  let relPackageConfig = projectConfigLocalPackages relConfig
  absHaddockOutputDir <- traverse makeAbsolute (packageConfigHaddockOutputDir relPackageConfig)
  return
    ( relConfig
        { projectConfigLocalPackages =
            relPackageConfig
              { packageConfigHaddockOutputDir = absHaddockOutputDir
              }
        }
    )

mkFlagsAbsolute :: NixStyleFlags ClientHaddockFlags -> IO (NixStyleFlags ClientHaddockFlags)
mkFlagsAbsolute relFlags = do
  let relHaddockFlags = haddockFlags relFlags
  absHaddockOutputDir <- traverse makeAbsolute (haddockOutputDir relHaddockFlags)
  return (relFlags{haddockFlags = relHaddockFlags{haddockOutputDir = absHaddockOutputDir}})

-- | The @haddock@ command is TODO.
--
-- For more details on how this works, see the module
-- "Distribution.Client.ProjectOrchestration"
haddockAction :: NixStyleFlags ClientHaddockFlags -> [String] -> GlobalFlags -> IO ()
haddockAction relFlags targetStrings globalFlags = do
  -- It's important to make --haddock-output-dir absolute since we change the working directory later.
  flags@NixStyleFlags{..} <- mkFlagsAbsolute relFlags

  let
    verbosity = fromFlagOrDefault normal (setupVerbosity $ configCommonFlags configFlags)
    installDoc = fromFlagOrDefault True (installDocumentation installFlags)
    flags' = flags{installFlags = installFlags{installDocumentation = Flag installDoc}}
    cliConfig = commandLineFlagsToProjectConfig globalFlags flags' mempty -- ClientInstallFlags, not needed here
  projCtx <- establishProjectBaseContext verbosity cliConfig HaddockCommand

  let relBaseCtx@ProjectBaseContext{projectConfig = relProjectConfig}
        | fromFlagOrDefault False (openInBrowser extraFlags) =
            projCtx{buildSettings = (buildSettings projCtx){buildSettingHaddockOpen = True}}
        | otherwise =
            projCtx
  absProjectConfig <- mkConfigAbsolute relProjectConfig
  let baseCtx = relBaseCtx{projectConfig = absProjectConfig}

  targetSelectors <-
    either (reportTargetSelectorProblems verbosity) return
      =<< readTargetSelectors (localPackages baseCtx) Nothing targetStrings

  buildCtx <-
    runProjectPreBuildPhase verbosity baseCtx $ \elaboratedPlan -> do
      when (buildSettingOnlyDeps (buildSettings baseCtx)) $
        dieWithException verbosity HaddockCommandDoesn'tSupport

      -- When we interpret the targets on the command line, interpret them as
      -- haddock targets
      targets <-
        either (reportBuildDocumentationTargetProblems verbosity) return $
          resolveTargets
            (selectPackageTargets haddockFlags)
            selectComponentTarget
            elaboratedPlan
            Nothing
            targetSelectors

      let elaboratedPlan' =
            pruneInstallPlanToTargets
              TargetActionHaddock
              targets
              elaboratedPlan
      return (elaboratedPlan', targets)

  printPlan verbosity baseCtx buildCtx

  progs <-
    reconfigurePrograms
      verbosity
      (haddockProgramPaths haddockFlags)
      (haddockProgramArgs haddockFlags)
      -- we need to insert 'haddockProgram' before we reconfigure it,
      -- otherwise 'set
      . addKnownProgram haddockProgram
      . pkgConfigCompilerProgs
      . elaboratedShared
      $ buildCtx
  let buildCtx' =
        buildCtx
          { elaboratedShared =
              (elaboratedShared buildCtx)
                { pkgConfigCompilerProgs = progs
                }
          }

  buildOutcomes <- runProjectBuildPhase verbosity baseCtx buildCtx'
  runProjectPostBuildPhase verbosity baseCtx buildCtx' buildOutcomes

-- | This defines what a 'TargetSelector' means for the @haddock@ command.
-- It selects the 'AvailableTarget's that the 'TargetSelector' refers to,
-- or otherwise classifies the problem.
--
-- For the @haddock@ command we select all buildable libraries. Additionally,
-- depending on the @--executables@ flag we also select all the buildable exes.
-- We do similarly for test-suites, benchmarks and foreign libs.
selectPackageTargets
  :: HaddockFlags
  -> TargetSelector
  -> [AvailableTarget k]
  -> Either TargetProblem' [k]
selectPackageTargets haddockFlags targetSelector targets
  -- If there are any buildable targets then we select those
  | not (null targetsBuildable) =
      Right targetsBuildable
  -- If there are targets but none are buildable then we report those
  | not (null targets) =
      Left (TargetProblemNoneEnabled targetSelector targets')
  -- If there are no targets at all then we report that
  | otherwise =
      Left (TargetProblemNoTargets targetSelector)
  where
    targets' = forgetTargetsDetail (map disableNotRequested targets)
    targetsBuildable = selectBuildableTargets (map disableNotRequested targets)

    -- When there's a target filter like "pkg:exes" then we do select exes,
    -- but if it's just a target like "pkg" then we don't build docs for exes
    -- unless they are requested by default (i.e. by using --executables)
    disableNotRequested t@(AvailableTarget _ cname (TargetBuildable _ _) _)
      | not (isRequested targetSelector (componentKind cname)) =
          t{availableTargetStatus = TargetDisabledByUser}
    disableNotRequested t = t

    isRequested (TargetPackage _ _ (Just _)) _ = True
    isRequested (TargetAllPackages (Just _)) _ = True
    isRequested _ LibKind = True
    --  isRequested _ SubLibKind = True --TODO: what about sublibs?

    -- TODO/HACK, we encode some defaults here as v2-haddock's logic;
    -- make sure this matches the defaults applied in
    -- "Distribution.Client.ProjectPlanning"; this may need more work
    -- to be done properly
    --
    -- See also https://github.com/haskell/cabal/pull/4886
    isRequested _ FLibKind = fromFlagOrDefault False (haddockForeignLibs haddockFlags)
    isRequested _ ExeKind = fromFlagOrDefault False (haddockExecutables haddockFlags)
    isRequested _ TestKind = fromFlagOrDefault False (haddockTestSuites haddockFlags)
    isRequested _ BenchKind = fromFlagOrDefault False (haddockBenchmarks haddockFlags)

-- | For a 'TargetComponent' 'TargetSelector', check if the component can be
-- selected.
--
-- For the @haddock@ command we just need the basic checks on being buildable
-- etc.
selectComponentTarget
  :: SubComponentTarget
  -> AvailableTarget k
  -> Either TargetProblem' k
selectComponentTarget = selectComponentTargetBasic

reportBuildDocumentationTargetProblems :: Verbosity -> [TargetProblem'] -> IO a
reportBuildDocumentationTargetProblems verbosity problems =
  case problems of
    [TargetProblemNoneEnabled _ _] -> do
      notice verbosity $
        unwords
          [ "No documentation was generated as this package does not contain a library."
          , "Perhaps you want to use the --haddock-all flag, or one or more of the"
          , "--haddock-executables, --haddock-tests, --haddock-benchmarks or"
          , "--haddock-internal flags."
          ]
      System.Exit.exitSuccess
    _ -> reportTargetProblems verbosity "build documentation for" problems
