Fix handling of packages with no planned components. (#110)

If a package is local to the project, but none of the components are in the plan, then there will be an empty `components` attribute and no `component-name`.  Currently this causes an error as we look for a `component-name` when the `components` attribute is empty.  This change will make it so that we only look for the `component-name` when there is no `components` attribute at all.

Author: hamishmack

plan2nix/Plan2Nix.hs

@@ -261,10 +261,15 @@ value2plan plan = Plan { packages, components, extras, compilerVersion, compiler
               nixComponentAttr = Text.pack . componentNameToHaskellNixAttr pkgName . Text.unpack
           in
             map ((quoted pkgName <> ".components.") <>) $
-              case (pkg ^. key "type" . _String, Map.keys (pkg ^. key "components" . _Object)) of
-                ("pre-existing", _) -> [ "library" ]
-                (_, []) -> [ nixComponentAttr $ pkg ^. key "component-name" . _String ]
-                (_, c)  -> map nixComponentAttr c)
+              if pkg ^. key "type" . _String == "pre-existing"
+                then [ "library" ]
+                else
+                  -- If a `components` attribute exists then the keys of that are the component names.
+                  -- If it does not exist then look for `component-name` instead.
+                  maybe
+                    [nixComponentAttr $ pkg ^. key "component-name" . _String]
+                    (map nixComponentAttr . Map.keys)
+                    (pkg ^? key "components" . _Object))
       $ Vector.toList (plan ^. key "install-plan" . _Array)
 
   -- Convert a cabal style component name to the haskell.nix attribute path.