Incorrect documentation

[respect]

Incorrect documentation

[nickl-]

Maybe the RouteInspector #63 should rather be exposed on the router, as this seems much more straight forward and usable then as a routine implementation.

It can be lazy loaded and accessed as follows: (for example)

<?php

            $path = r3->inspector->active->uri;

            $parseValues = r3->inspector->active->turiTemplate->parseUrl($path};

             $r3->inspector->reset();
             while (r3->inspector->isValid())  {
                    foreach (r3->inspector->current()->routines as $routine)
                             foreach ($routine->types as $routineType)
                                       echo "$routine - $routineType\n";

                     r3->inspector->next();
             }

             foreach (r3->inspector as $routine)
                   echo $routine,
                        "\nIs active: ",
                         var_export($routine->active),
                         PHP_EOL,
                         "HTTP verbs: ",
                         implode(',', $routine->methods);

Has anyone had a chance to look at the route-inspector branch yet? Can I have some feedback please!

[alganet]

I like the inspecting approach, but for now we could expose the last dispatched request on the router as well, while the RouteInspector gets more stable. I believe it's a simple fix (I'll do this one by the end of the week!) The request may be useful for things-that-are-not-routy. What do you think?

[alganet]

Finally had a time window to fixed that, should work like the docs now!