gingersnap 0.1.2.0 → 0.1.3.0
raw patch · 2 files changed
+7/−5 lines, 2 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
+ Gingersnap.Core: Rsp :: ShouldCommitOrRollback -> RspPayload -> Rsp
+ Gingersnap.Core: RspPayload_Bad :: e -> RspPayload
+ Gingersnap.Core: RspPayload_Custom :: Status -> ByteString -> ByteString -> RspPayload
+ Gingersnap.Core: RspPayload_Empty :: RspPayload
+ Gingersnap.Core: RspPayload_Good :: x -> RspPayload
+ Gingersnap.Core: ShouldCommit :: ShouldCommitOrRollback
+ Gingersnap.Core: ShouldRollback :: ShouldCommitOrRollback
+ Gingersnap.Core: [rspPayload] :: Rsp -> RspPayload
+ Gingersnap.Core: [rspShouldCommit] :: Rsp -> ShouldCommitOrRollback
+ Gingersnap.Core: data RspPayload
+ Gingersnap.Core: data ShouldCommitOrRollback
Files
- gingersnap.cabal +1/−1
- src/Gingersnap/Core.hs +6/−4
gingersnap.cabal view
@@ -1,5 +1,5 @@ name: gingersnap-version: 0.1.2.0+version: 0.1.3.0 synopsis: snap-core + aeson + postgresql-simple = delicious description: JSON API idioms for snap-core, preventing DB connection leaks license: BSD3
src/Gingersnap/Core.hs view
@@ -11,10 +11,7 @@ , ApiErr(..) , ErrResult(..) - , Rsp -- (..) -- Maybe export this and 'ShouldCommitOrRollback' in the future- -- TODO: move these lower in export list for Haddocks:- -- , RspPayload- -- , ShouldCommitOrRollback(..)+ , Rsp(..) , rspGood , rspBad@@ -33,6 +30,11 @@ , rspIsGood , errorEarlyCode++ -- These won't typically be inspected by hand but there's no reason we should+ -- block people from inspecting them if they like+ , RspPayload(..)+ , ShouldCommitOrRollback(..) -- Maybe?: -- , module import Network.HTTP.Types.Status