bidi

bidi copied to clipboard

Readme should show basic example with empty path

1

Currently most of the examples in the README expect something after the `/`. Given that matching the "empty path" is a very common scenario users will want to accomplish it...

martinklepsch

RegExp flags not respected by match-pattern

1

This issue came up while I tried to setup a case insensitive PatternSegment in my routing table. Clojurescript re-pattern implementation handle's java style regex flags by picking them off the...

olivergeorge

MapEntry conflict due to prismatic/schema

1

Building with clojurescript 1.9.671 leads to aborted execution on node after compilation warning: ->MapEntry already refers to: cljs.core/->MapEntry being replaced by: schema.core/->MapEntry Remedy by upgrading prismatic/schema dependency to the latest...

njordhov

Regex extractors don't behave as expected

4

While attempting to resolve an issue regarding a typical url encoded path `test/user%2B"` I discovered that `match-route` function was returning nil. `(bidi/match-route ["/" {"test/" {[:slug] :om/details}}] "/test/user%2B")` Looking into the...

bjconlan

With 2 separate vhost routes, for the same host, but with different schemes, bidi will match on both sets of routes. But should only match on one. This looks suspicious...

SevereOverfl0w

Recursive routes possible?

4

I am trying to route a rest-like url with variable path params, is this possible?

dustingetz

match-route fails for %20 space representation

3

Basic Example: ``` (def routes ["/" {[:foo] :bar}]) (match-route routes "/Test") => {:route-params {:foo "Test"}, :handler :bar} (match-route routes "/Test%20Project") => nil ```

deadghost

Get required parameters for handler

1

Currently, bidi has the `path-for` function which will give a url for a handler with parameters, but it returns an error if not all of the parameters are in the...

shader

URI in request should be decoded prior to matching

4

A uri that includes encoded characters must be matched un-decoded. While this is is possible, it is hardly ideal. An example request ``` {:server-port 80, :server-name "localhost", :remote-addr "localhost", :uri...

cch1

Why does this not work? ``` (bidi/match-route ["/" {[[#"-?[0-9]+(\.[0-9]+)?" :lat] "%7C" [#"-?[0-9]+(\.[0-9]+)?" :lng] "%7C" [#"[0-9]+(\.[0-9]+)?" :radius]] {"/b" :geo}}] "/38.0%7C-78.5%7C10.0/b") => {:route-params {:lat "38.0", :lng "%7C", :radius ".5"}, :handler :geo} ```...

cch1