can one add coercion via custom expanders? I’m trying to keep my routes code-free (i.e. data only), so I can store them in EDN files.

interesting @levitanong. You could do that, or if you have just one coercion per app, you can set it in a router:

(ring/router
  my-routes-from-edn
  {:data {:coercion spec-coercion}})

the :data gets merged to all routes.

The new Trie is merged into master. Was fun optimizing the internals - now 20x faster than the original (Pedestal) version.

I went ahead and made the custom expander and I'm happy to report that it works. However your method is much more pleasing to me, so I'll go with that. :) thanks!

@haiyuan.vinurs https://github.com/metosin/reitit/commit/5713afac34ec5ea0972b731a69b0d3cdcefc9b46

so, we stuffed routes into a PersistenHashMap, which for sure, lost the order. The new code forces the routes into a PersistentArrayMap, which has the order. It might be lost again in json-serialization, but might also just work.

there is [metosin/reitit "0.3.0-SNAPSHOT"] to test that (among others)

@ikitommi thanks very much, i tested it just now, it works ok

["/{🌈}:thinking_face:/🎈" ::emoji] next level

@ikitommi testing 0.3.0.

(r/match-by-name (r/router [["" :google]]) :google)

;; #reitit.core.PartialMatch{:template "", :data {:name :google}, :result nil, :path-params nil, :required #{:}}

@levitanong really odd match indeed :)