packages feed

json-spec-elm 0.4.0.1 → 0.4.0.2

raw patch · 2 files changed

+18/−7 lines, 2 filesdep ~json-specPVP ok

version bump matches the API change (PVP)

Dependency ranges changed: json-spec

API changes (from Hackage documentation)

Files

json-spec-elm.cabal view
@@ -1,6 +1,6 @@ cabal-version:       3.0 name:                json-spec-elm-version:             0.4.0.1+version:             0.4.0.2 synopsis:            Elm code generate for `json-spec`. description:                               Produce elm types, encoders, and decoders from a@@ -24,7 +24,7 @@     , base                 >= 4.17.2.1 && < 4.20     , containers           >= 0.6.7    && < 0.7     , elm-syntax           >= 0.3.2.0  && < 0.4-    , json-spec            >= 0.3.0.0  && < 0.4+    , json-spec            >= 0.3.0.0  && < 0.6     , text                 >= 2.0.2    && < 2.2  common warnings@@ -46,13 +46,13 @@   ghc-options:     -Wunused-packages   build-depends:-    , bound                >= 2.0.7    && < 2.1-    , mtl                  >= 2.2.2    && < 2.4+    , bound                >= 2.0.7 && < 2.1+    , mtl                  >= 2.2.2 && < 2.4  flag compile-elm   description:-    Set this flag to run the Elm compilation tests, which requires-    Elm to be installed on the system.+    Set this flag to run the Elm compilation tests, which requires Elm+    to be installed on the system.   default: False  test-suite compile-elm
test/test-pass.hs view
@@ -1,4 +1,15 @@ module Main (main) where  main :: IO ()-main = pure ()+main =+  putStrLn $+    unlines+      [ ""+      , ""+      , "    NB! We are _NOT_ really running the tests because the"+      , "    `compile-elm` flag is not set. If you are sure that the"+      , "    proper Elm tools are installed on the system, then you can"+      , "    set the `compile-elm` flag and real tests will be run."+      , ""+      , ""+      ]