Sadly, with the benefit of hindsight, this wasn't a good idea.

There are two reasons we're dropping this:

  - It doesn't play nicely with libraries like `Rack::Builder`, which
    dispatches requests to different Rack apps based on a path prefix in
    a way that isn't visible to middleware.

    For example, when using `Rack::Builder`, `sinatra.route` only
    contains the parts of the path after the prefix that `Rack::Builder`
    used to dispatch to the specific app, and doesn't leave any
    information in the request environment to indicate which prefix it
    dispatched to.
  - It turns out framework-specific route info isn't always formatted in
    a way that looks good in a Prometheus label.

    For example, when using regex-based route-matching in Sinatra, you
    can end up with labels that look like `\\/vapes\\/([0-9]+)\\/?`.

For a really detailed dive into those two issues, see this GitHub
comment:

#249 (comment)

Signed-off-by: Chris Sinjakli <chris@sinjakli.co.uk>

Signed-off-by: Chris Sinjakli <chris@sinjakli.co.uk>