purescript-bridge: Generate PureScript data types from Haskell data types

[ bsd3, library, web ] [ Propose Tags ]
Versions [RSS] 0.1.0.0, 0.3.0.0, 0.3.0.2, 0.3.0.3, 0.3.0.4, 0.3.0.5, 0.3.0.6, 0.3.1.0, 0.3.1.1, 0.3.2.0, 0.4.0.0, 0.6.0.0, 0.6.0.1, 0.6.0.2, 0.7.0.0, 0.7.0.1, 0.8.0.0, 0.8.0.1, 0.9.0.0, 0.10.0.0, 0.10.1.0, 0.11.0.0, 0.11.1.0, 0.11.1.1, 0.11.1.2, 0.12.0.0, 0.13.0.0, 0.14.0.0, 0.15.0.0
Dependencies base (>=4.8 && <=5.1), containers, directory, filepath, generic-deriving, lens, mtl, text, transformers [details]
License BSD-3-Clause
Author Robert Klotzner
Maintainer robert . klotzner A T gmx . at
Category Web
Source repo head: git clone https://github.com/eskimor/purescript-bridge.git
Uploaded by eskimo at 2016-09-05T11:04:30Z
Distributions LTSHaskell:0.15.0.0, NixOS:0.15.0.0, Stackage:0.15.0.0
Reverse Dependencies 1 direct, 1 indirect [details]
Downloads 20819 total (85 in the last 30 days)
Rating 1.25 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2016-09-05 [all 1 reports]

Readme for purescript-bridge-0.7.0.1

[back to package description]

purescript-bridge

Build Status

Translate your Haskell types to PureScript types. It should in theory work for almost all Haskell types, including type constructors! You just have to instantiate it with dummy parameters from e.g. "Language.PureScript.Bridge.TypeParameters".

Data type translation is fully and easily customizable by providing your own BridgePart instances!

JSON encoding / decoding

For compatible JSON representations you should be using aeson's generic encoding/decoding with default options and encodeJson and decodeJson from "Data.Argonaut.Generic.Aeson" in purescript-argonaut-generic-codecs.

Documentation

Usage of this library is documented in Language.Purescript.Bridge.

All you should need to get started is: writePSTypes.

Status

This library is at a quite early stage. It works for my use case at the moment and I will fix bugs when they come along. Also PRs for more PSTypes definitions and bridges are very welcome!

Expect bugs - especially for more advanced use cases. Although I have tested the most advanced one already with no issues, bugs always creep in.