Enumerate registered versions about grape HOT 3 CLOSED

You could use RouteSet methods for route listing and then parse results:

Test::API.instance_eval {route_set.instance_eval{@routes.map{|r| r.conditions} }}

or apply this commit
presskey@e58af95
and use:

Test::API.structure

from grape.

The reverse engineering of routes turned out to be too messy. Instead, I chose to collect those versions in an array as they are defined and do the same for routes. See #48.

The code that you're pointing to has many issues as soon as the api gets a bit more complicated. If you're interested in examples, run it through tests in dblock@767638f. You can see a version in that commit of your code expanded to support more grape-valid scenarios. I basically gave up on trying to build any kind of nested structure at that point - having a set of routes is much easier and that set can always be turned into a tree if someone really wants to.

from grape.

This has become #53, I am going to close this.

from grape.