servant-reason alternatives and similar packages
Based on the "servant" category.
Alternatively, view servant-reason alternatives based on common mentions on social networks and blogs.
-
servant
Main repository for the servant libraries — DSL for describing, serving, querying, mocking, documenting web applications and more! -
servant-elm
Automatically derive Elm functions to query servant webservices -
servant-purescript
Translate servant API to purescript code, with the help of purescript-bridge. -
servant-swagger-ui
Provide embedded swagger UI for servant and swagger -
servant-response
Moved to http://github.com/haskell-servant -
servant-js
Automatically derive javascript functions to query servant webservices. -
servant-auth-cookie
Authentication via encrypted cookies -
servant-aeson-specs
Generically obtain tests for JSON serialization -
servant-pagination
Type-safe pagination for Servant APIs -
servant-pandoc
Render a servant API to Pandoc's native representation -
servant-github-webhook
Servant combinators for writing secure GitHub webhooks -
servant-mock
Derive a mock server for free from your servant API types -
servant-matrix-param
Matrix parameter combinator for servant -
servant-auth-token-acid
Servant based API and server for token based authorisation -
servant-auth-token-leveldb
Servant based API and server for token based authorisation -
servant-jsonrpc
Tools to build JSON-RPC clients and servers the Servant way -
servant-match
Standalone implementation of servant’s dispatching mechanism -
servant-kotlin
Automatically derive Kotlin functions to query servant webservices -
servant-http2-client
Generate http2-client from Servant APIs -
servant-ruby
Create a Ruby client from a Servant API using Net::HTTP. -
servant-options
Provide responses to OPTIONS requests for Servant applications. -
servant-generate
Generate default implementations for servers in a flexible way (a.k.a servant-mock on steroids) -
servant-haxl-client
automatical derivation of querying functions for servant webservices -
servant-proto-lens
Servant Content-Type for proto-lens protobuf modules. -
servant-multipart
multipart/form-data (e.g file upload) support for servant
Collect and Analyze Billions of Data Points in Real Time
Do you think we are missing an alternative of servant-reason or a related project?
README
Servant Reason
Automatically derive bindings for Servant APIs in Reason. Originally build by converting servant-elm to Reason. Types are generated using reason-export.
More docs on Hackage.
A full example of how to integrate Servant and Reason is available at servant-reason-example.
Usage
Run the tests if you want a concrete example. They will build a _test-cache directory that contains a sample Reason repository for a servant API. test also contain example output files for different kinds of bindings.
Usage is simple and automatic. If you have an API like the one below
{-# LANGUAGE DataKinds #-}
{-# LANGUAGE DeriveGeneric #-}
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE TypeOperators #-}
import Reason (Spec (Spec), specsToDir, toReasonDecoderSource,
toReasonTypeSource)
import GHC.Generics (Generic)
import Servant.API ((:>), Capture, Get, JSON)
import Servant.Reason (ReasonType, Proxy (Proxy), defReasonImports,
generateReasonForAPI)
data Book = Book
{ name :: String
} deriving (Generic)
instance ReasonType Book
type BooksApi = "books" :> Capture "bookId" Int :> Get '[JSON] Book
You can expose your API to reason with:
module Main where
import Data.Proxy
import Reason
import Data.Text hiding (intercalate, map)
import Db
main :: IO ()
main = do
let code = defReasonImports
: toReasonTypeSource (Proxy :: Proxy Book)
: toReasonDecoderSource (Proxy :: Proxy Book)
: generateReasonForAPI (Proxy :: Proxy BooksApi))
writeFile "Api.re" $ intercalate "\n\n" $ map unpack code
That's it. You can now include Api.re
in a Reason project.
Reason setup
The generated code needs access to two Reason libraries @glennsl/bs-json and bs-fetch. Get the latest install instructions from the upstream repos, but at the time of writing these were:
npm install --save @glennsl/bs-json
npm install --save bs-fetch
Then add @glennsl/bs-json
and bs-fetch
to bs-dependencies
in your bsconfig.json
:
{
...
"bs-dependencies": ["@glennsl/bs-json", "bs-fetch"]
}