dash-haskell 1.0.0.1 → 1.0.0.2

raw patch · 4 files changed

+6/−14 lines, 4 filesdep ~optparse-applicative

Dependency ranges changed: optparse-applicative

Files

• dash-haskell.cabal +2/−2
• src/Main.hs +1/−1
• src/Options/CabalConstraints.hs +1/−1
• src/Pipes/FileSystem.hs +2/−10

@@ -1,5 +1,5 @@ name:                dash-haskell-version:             1.0.0.1+version:             1.0.0.2 synopsis:            Command line tool to generate Dash docsets (IDE docs) from package haddock homepage:            http://www.github.com/jfeltz/dash-haskell Bug-reports:         https://github.com/jfeltz/dash-haskell/issues@@ -130,7 +130,7 @@                      , either               >= 4.3                      , ghc                  >= 7.8.3                      , mtl                  >= 2.1.3.1-                     , optparse-applicative >= 0.10.0+                     , optparse-applicative >= 0.10.0 && < 0.11                      , pipes                >= 4.1.0                      , process              >= 1.2.0.0                      , sqlite-simple        >= 0.4.5.0

@@ -34,6 +34,6 @@   where     parserInfo :: ParserInfo Options    parserInfo = info (helper <*> parser)  $-     header "dash-haskell v1.0.0.1, a dash docset construction tool for Haskell packages"+     header "dash-haskell v1.0.0.2, a dash docset construction tool for Haskell packages"      <> progDesc "additional help is available with \"dash-haskell help <topic|option>\""      <> footer "http://www.github.com/jfeltz/dash-haskell (C) John P. Feltz 2014"

@@ -38,7 +38,7 @@ suites' s     = none { suites = s }   -- | Parser for the cabal constraints option.--- Note: I don't think this can be simpliifed with sepBy since the +-- Note: I don't think this can be simplified with sepBy since the  -- non-sep parser may fail, causing input and positioning to be lost. -- If someone knows a better way, please advise/patch. constraints :: Maybe Constructor -> Parser CabalConstraints 

@@ -23,15 +23,7 @@ import           Haddock.Artifact import           Haddock.Sqlite --- | See:--- https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html-data Plist = Plist-    { cfBundleIdentifier   :: String-    , cfBundleName         :: String-    , docSetPlatformFamily :: String-    } deriving Show---- TODO/FIXME the utility of some of these fields are still unclear to me,+-- TODO the utility of some of these fields is still unclear to me, -- at the moment they are filled simply to satisfy the docset spec. plist :: Ghc.PackageId -> BS.ByteString plist p = Data.ByteString.Char8.pack . unlines $@@ -205,7 +197,7 @@     <-< pipe_htmlConvert (pkg conf)     <-< leafs (\p -> P.extension p /= Just "haddock") (htmlDir conf)   -  -- FIXME/TODO Since the haddock index is already produced in source docs+  -- TODO Since the haddock index is already produced in source docs   -- with latest packaging systems, this is likely unnecessary    -- liftIO $ do    --    putStrLn "running haddock indexes"