Safe Haskell | None |
---|---|
Language | Haskell2010 |
This package provides a simple framework for routing and responses. The two primary goals are:
- All web handler functions are just plain IO. There is no Fn monad, or monad transformer. This has a lot of nice properties, foremost among them is that it is easier to call handlers from other contexts (like GHCi, when testing, in other threads, etc). As a result, these functions take a single extra parameter that has the context that they need (like database connection pools, the request, etc).
- Web handlers are functions with typed parameters. When routing, we specify many parameters (most commonly, numeric ids, but can be many things), so the handlers should be functions that take those as parameters.
- class RequestContext ctxt where
- requestLens :: Functor f => (Request -> f Request) -> ctxt -> f ctxt
- getRequest :: ctxt -> Request
- setRequest :: ctxt -> Request -> ctxt
- toWAI :: RequestContext ctxt => ctxt -> (ctxt -> IO Response) -> Application
- type Req = ([Text], Query)
- route :: RequestContext ctxt => ctxt -> [ctxt -> Maybe (IO (Maybe Response))] -> IO (Maybe Response)
- fallthrough :: IO (Maybe Response) -> IO Response -> IO Response
- (==>) :: RequestContext ctxt => (Req -> k -> Maybe (Req, ctxt -> a)) -> k -> ctxt -> Maybe a
- (//) :: (r -> k -> Maybe (r, k')) -> (r -> k' -> Maybe (r, a)) -> r -> k -> Maybe (r, a)
- (/?) :: (r -> k -> Maybe (r, k')) -> (r -> k' -> Maybe (r, a)) -> r -> k -> Maybe (r, a)
- path :: Text -> Req -> a -> Maybe (Req, a)
- end :: Req -> a -> Maybe (Req, a)
- anything :: Req -> a -> Maybe (Req, a)
- segment :: FromParam p => Req -> (p -> a) -> Maybe (Req, a)
- class FromParam a where
- fromParam :: Text -> Either ParamError a
- data ParamError
- param :: FromParam p => Text -> Req -> (p -> a) -> Maybe (Req, a)
- paramMany :: FromParam p => Text -> Req -> ([p] -> a) -> Maybe (Req, a)
- paramOpt :: FromParam p => Text -> Req -> (Either ParamError [p] -> a) -> Maybe (Req, a)
- okText :: Text -> IO (Maybe Response)
- okHtml :: Text -> IO (Maybe Response)
- errText :: Text -> IO (Maybe Response)
- errHtml :: Text -> IO (Maybe Response)
- notFoundText :: Text -> IO Response
- notFoundHtml :: Text -> IO Response
- redirect :: Text -> IO (Maybe Response)
Application setup
class RequestContext ctxt where Source
Specify the way that Fn can get the Request out of your context.
The easiest way to instantiate this is to use the lens, but if you
don't want to use lenses, define getRequest
and setRequest
.
Note that requestLens
is defined in terms of getRequest
and
setRequest
and vice-versa, so you need to define _one_ of these.
Nothing
requestLens :: Functor f => (Request -> f Request) -> ctxt -> f ctxt Source
getRequest :: ctxt -> Request Source
setRequest :: ctxt -> Request -> ctxt Source
toWAI :: RequestContext ctxt => ctxt -> (ctxt -> IO Response) -> Application Source
Convert an Fn application (provide a context, a context to response function and we'll create a WAI application by updating the Request value for each call).
Routing
route :: RequestContext ctxt => ctxt -> [ctxt -> Maybe (IO (Maybe Response))] -> IO (Maybe Response) Source
The main construct for Fn, route
takes a context (which it will pass
to all handlers) and a list of potential matches (which, once they
match, may still end up deciding not to handle the request - hence
the double Maybe
). It can be nested.
app c = route c [ end ==> index , path "foo" / path "bar" segment ? param "id ==> h] where index :: IO (Maybe Response) index = okText "This is the index." h :: Text -> Text -> IO (Maybe Response) h s i = okText ("got path foo" <> s <> ", with id=" <> i)
fallthrough :: IO (Maybe Response) -> IO Response -> IO Response Source
The route
function (and all your handlers) return
'IO (Maybe Response)', because each can elect to not respond (in
which case we will continue to match on routes). But to construct
an application, we need a response in the case that nothing matched
- this is what fallthrough
does.
(==>) :: RequestContext ctxt => (Req -> k -> Maybe (Req, ctxt -> a)) -> k -> ctxt -> Maybe a Source
The connective between route patterns and the handler that will be called if the pattern matches. The type is not particularly illuminating, as it uses polymorphism to be able to match route patterns with varying numbers (and types) of parts with functions of the corresponding number of arguments and types.
(//) :: (r -> k -> Maybe (r, k')) -> (r -> k' -> Maybe (r, a)) -> r -> k -> Maybe (r, a) Source
Connects two path segments. Note that when normally used, the
type parameter r is Req
. It is more general here to facilitate
testing.
(/?) :: (r -> k -> Maybe (r, k')) -> (r -> k' -> Maybe (r, a)) -> r -> k -> Maybe (r, a) Source
Identical to '(//)', provided simply because it serves as a
nice visual difference when switching from 'path'/'segment' to
param
and friends.
path :: Text -> Req -> a -> Maybe (Req, a) Source
Matches a literal part of the path. If there is no path part left, or the next part does not match, the whole match fails.
end :: Req -> a -> Maybe (Req, a) Source
Matches there being no parts of the path left. This is useful when matching index routes.
segment :: FromParam p => Req -> (p -> a) -> Maybe (Req, a) Source
Captures a part of the path. It will parse the part into the type specified by the handler it is matched to. If there is no segment, or if the segment cannot be parsed as such, it won't match.
data ParamError Source
param :: FromParam p => Text -> Req -> (p -> a) -> Maybe (Req, a) Source
Matches on a single query parameter of the given name. If there is no parameters, or it cannot be parsed into the type needed by the handler, it won't match.
paramMany :: FromParam p => Text -> Req -> ([p] -> a) -> Maybe (Req, a) Source
Matches on query parameters of the given name. If there are no parameters, or it cannot be parsed into the type needed by the handler, it won't match.
paramOpt :: FromParam p => Text -> Req -> (Either ParamError [p] -> a) -> Maybe (Req, a) Source
If the specified parameters are present, they will be parsed into the type needed by the handler, but if they aren't present or cannot be parsed, the handler will still be called.
Responses
errHtml :: Text -> IO (Maybe Response) Source
Returns Html (in Text
) as a response with a 500 status code.
notFoundText :: Text -> IO Response Source
Returns a 404 with the given Text
as a body. Note that this
returns a 'IO Response' not an 'IO (Maybe Response)' because the
expectaiton is that you are calling this with fallthrough
.
notFoundHtml :: Text -> IO Response Source
Returns a 404 with the given html as a body. Note that this
returns a 'IO Response' not an 'IO (Maybe Response)' because the
expectaiton is that you are calling this with fallthrough
.