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 better UX and for people with bad eyesight it makes sense to change the color of the current position icon in different states:

• GPS position is known and actual
• GPS position is not detected yet, but OM tries to find it
• GPS position is turned off and not active

Let's decide on colors (they should be clearly recognizable on top of the map).

In zebra/rt_netlink.c, we call vrf_lookup_by_id() when we get a route to find the associated vrf object for that table.

This should be improved to be a hash table mapping of Table ID to zebra_vrf object.

You would need to create a hash table probably in zebra/zebra_vrf.h that uses the table_id hash as a key and then update the code in vrf_lookup_by_id() to use this.

This shoul

recently ran a US tomtom dataset where we were handling ferries pretty naively and valhalla attempted to build a 24 000 km shortcut 😂

2021/12/20 21:33:30.842885 [INFO] Done HierarchyBuilder
2021/12/20 21:33:30.846544 [INFO] Creating shortcuts on level 1
2021/12/20 21:35:21.394332 [ERROR] Exceeding max. edge length: 24087463
terminate called after throwing an instance of 'std::runti

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