Is the route property intentionally missing from the `Match` API?
steinybot opened this issue · comments
I just noticed while debugging that the Match
has route
and routes
properties. Only routes
is on the TS type. Was route
meant to be part of the public API too? It is often the most useful part and having quick access to it rather than pulling out the last element from the routes
array would be convenient.