Hackage :: [Package]

Metadata revisions for web-inv-route-0.1

Package maintainers and Hackage trustees are allowed to edit certain bits of package metadata after a release, without uploading a new tarball. Note that the tarball itself is never changed, just the metadata that is stored separately. For more information about metadata revisions, please refer to the Hackage Metadata Revisions FAQ.

No. Time User SHA256
-r2 (web-inv-route-0.1-r2) 2019-06-01T08:52:08Z HerbertValerioRiedel 9a2bee1a0cef02192826329d5bf0aa5af7b7bbdb07ca00c5c1be9a7b5b0b6d08

  • Changed the library component's library dependency on 'base' from 

    >=4.8 && <5
    to 
    >=4.8 && <4.11
-r1 (web-inv-route-0.1-r1) 2016-08-24T18:25:01Z DylanSimon 7e68be5f41dbc5f47d7f38f017f0f676eaf962a8fa56142ce491c8882165d28d

  • Changed description from 

    Utilities to route HTTP requests, mainly focused on path components.  Routes are specified using bijections and invariant functors, allowing run-time composition (routes can be distributed across modules), reverse and forward routing derived from the same specification, and O(log n) lookups.

There are four steps/components of this package.

1. Route endpoint specification: "Web.Route.Invertible.Common"
2. Route map construction: "Web.Route.Invertible.Common"
3. Route map lookup: "Web.Route.Invertible" (for the generic interface), "Web.Route.Invertible.Wai", "Web.Route.Invertible.Snap", or "Web.Route.Invertible.Happstack"
4. Reverse routing: "Web.Route.Invertible" or "Web.Route.Invertible.URI"

Most users will just want to import a framework-specific module like "Web.Route.Invertible.Wai" (or the generic "Web.Route.Invertible"), each of which re-exports "Web.Route.Invertible.Common".
See test/Main.hs for some examples.
    to 
    Utilities to route HTTP requests, mainly focused on path components.  Routes are specified using bijections and invariant functors, allowing run-time composition (routes can be distributed across modules), reverse and forward routing derived from the same specification, and O(log n) lookups.

There are four steps/components of this package.

1. Route endpoint specification: "Web.Route.Invertible.Common"

2. Route map construction: "Web.Route.Invertible.Common"

3. Route map lookup: "Web.Route.Invertible" (for the generic interface), "Web.Route.Invertible.Wai", "Web.Route.Invertible.Snap", or "Web.Route.Invertible.Happstack"

4. Reverse routing: "Web.Route.Invertible" or "Web.Route.Invertible.URI"

Most users will just want to import a framework-specific module like "Web.Route.Invertible.Wai" (or the generic "Web.Route.Invertible"), each of which re-exports "Web.Route.Invertible.Common".
See test/Main.hs for some examples.

  • Changed the library component's library dependency on 'network-uri' from 

    >=0
    to 
    >=2.6.1
-r0 (web-inv-route-0.1-r0) 2016-05-23T15:24:48Z DylanSimon 7749c82609ebd93605164fa25a22f6ab0e633b50c588343ea72a45a7d59afe46