The route-generator package

Most of the defacto Haskell web routing libraries are either linear
in complexity, or require lots of extra extensions, like Template
Haskell.

Luckily, yesod-routes has Yesod.Routes.Dispatch, which is a very clean,
efficient, and extension-free router. Writing routes out in code can,
however, be quite verbose. This utility is a code generator to produce
routes compatible with Yesod.Routes.Dispatch from a nice input format.

Example:

GET / => home
GET /post/: => showPost
PUT /* => updateSomething

./routeGenerator -r -m SomeModule routes.txt

Will generate routes that map the correct HTTP verb (which you should
pass as a prepended path segment to your Dispatch) and path to
functions imported from the module specified in the second parameter.

A colon matches any path segment, and passes the matched segment
through to the specified function, passing each match segment in order.
The expected type of the segment is inferred from the type of the
function. If the segment cannot be parsed as that type, the path does
not match. Parsing is done with Web.PathPieces.fromPathPiece.

An asterisk at the end of the path causes rhHasMulti to be set to True,
meaning that any path segments after what has been specified will be
allowed.

Downloads

Maintainer's Corner

Readme for route-generator

Readme for route-generator-0.3.1

Most of the defacto Haskell web routing libraries are either linear
in complexity, or require lots of extra extensions, like Template
Haskell.
Luckily, yesod-routes has Yesod.Routes.Dispatch, which is a very clean,
efficient, and extension-free router. Writing routes out in code can,
however, be quite verbose. This utility is a code generator to produce
routes compatible with Yesod.Routes.Dispatch from a nice input format.
Example:
> GET / => home
> GET /post/: => showPost
> PUT /* => updateSomething
> ./routeGenerator -r -m SomeModule routes.txt
Will generate routes that map the correct HTTP verb (which you should
pass as a prepended "path segment" to your Dispatch) and path to
functions imported from the module specified in the second parameter.
A colon matches any path segment, and passes the matched segment
through to the specified function, passing each match segment in order.
The expected type of the segment is inferred from the type of the
function. If the segment cannot be parsed as that type, the path does
not match. Parsing is done with Web.PathPieces.fromPathPiece.
An asterisk at the end of the path causes rhHasMulti to be set to True,
meaning that any path segments after what has been specified will be
allowed.