routing

Context and Description

The READMEs and any example code in all projects should be updated to reflect the move from the IBM-Swift organization to the Kitura organization.

If anyone wants to take on all or part of this, please comment here so other's know what you're working on and submit PR's. :-)

Thanks!

I have defined this route using Fluro. exchange/:pair

There is a problem! I want :pair to be optional. If client types https://host:port/exchange/BNB_BTC everything goes fine. but assume the user is looking for https://host:port/exchange and he confronts with 404 error cause there is no such route/path.

I mean something like exchange/{:pair}.

For example, contact:facebook or contact:instagram tags are ignored now. The full list is available here:
https://wiki.openstreetmap.org/wiki/Key:contact

If add some routes:

ip route 1.1.1.1/32 2.2.2.3
ip route 1.1.1.1/32 2.2.2.2
ip route 1.1.1.1/32 2.2.2.4

In config they sorted by gateway:

# do show running-config 
...
Current configuration:
!
frr version 8.1-dev
...
ip route 1.1.1.1/32 2.2.2.4
ip route 1.1.1.1/32 2.2.2.3
ip route 1.1.1.1/32 2.2.2.2

But when added ip route 1.1.1.1/32 2.2.2.1, he will adde

Swagger feature docstring (and spec?) places tags on route-data root:

https://github.com/metosin/reitit/blob/master/modules/reitit-swagger/src/reitit/swagger.cljc#L55

Examples place tags key under swagger:

https://github.com/metosin/reitit/blob/master/examples/ring-swagger/src/example/server.clj#L30

Both seem to generate proper swagger.json, but first one fails spec validation. Why? Sp