Currently canned resolves the routes on request, which is great since they can be modified while canned is running without any problems, adding new files/folders/etc. One thing missing so is the option to actually list what is available, currently this is mostly done by using tree to show the folder structure of the example folder, which prints something like this:
Sadly this does not take into account the rules canned has to resolve the paths, it would be awesome to get something like this:
example(master*)$ canned routes
verb path
GET /search
PUT /comment/1
...
This means crawling the current file tree and resolving the routes and print.
Currently canned resolves the routes on request, which is great since they can be modified while canned is running without any problems, adding new files/folders/etc. One thing missing so is the option to actually list what is available, currently this is mostly done by using
treeto show the folder structure of the example folder, which prints something like this:Sadly this does not take into account the rules canned has to resolve the paths, it would be awesome to get something like this:
This means crawling the current file tree and resolving the routes and print.