react-flux-servant: Allow react-flux stores to send requests to a servant server

[ bsd3, library, web ] [ Propose Tags ]

See the README below.

[Skip to Readme]




Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


  • No Candidates
Versions [RSS] 0.1.0, 0.1.1
Change log
Dependencies aeson (>=0.8), base (>=4.8 && <5), ghcjs-base, react-flux (>=1.2 && <1.3), servant (>=0.7), text (>=1.2) [details]
License BSD-3-Clause
Author John Lenz <>
Maintainer John Lenz <>
Category Web
Home page
Source repo head: hg clone
Uploaded by JohnLenz at 2016-11-23T22:53:46Z
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 1420 total (3 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2016-11-23 [all 1 reports]

Readme for react-flux-servant-0.1.1

[back to package description]

This project integrates react-flux with servant. There is a small example in the haddock documentation. To depend on this module, I add it to the extra-deps in my project's stack.yaml. See the react-flux documentation for a full example stack.yaml.

At the moment the code works well and is straightforward to integrate into a react-flux store; I am using it in production. Having said that, the current API requires you to create two store actions for each request and it is somewhat tedious to write all this boilerplate. At some point, I would like to build a better API, perhaps one that takes better advantage of the type-level Servant.API definitions to drastically reduce the boilerplate. Unfortunately, since it currently works (and even works well, the existing API is good), due to time constraints it might be awhile before I get around to thinking about better APIs. If you have any ideas for a better API, even if you don't have any code, please open an issue!