Feature - Routes as Objects about klein.php

[unstoppablecarl]

That would be sexy. I don't know what the performance cost of __invoke() would be though

[Rican7]

I'm not incredibly concerned with the performance characteristics of __invoke(), only because most projects (insert made-up percentage statistic here) don't use the return value of the respond() method anyway, and even so would most likely not use it in performance-heavy tasks or in multiple places.

Besides, I think that the benefits of "classifying" the route callbacks outweigh the potential performance hit that correlates with a small percentage of developers actually using the respond() return value. 👅

I'm glad you like the idea, though. And yea, questioning performance is never a bad idea.

[Rican7]

Boom! So far this is coming along nicely in my branch: https://github.com/Rican7/klein.php/tree/feature/routes-as-objects

I have a new Route class and the Klein respond() method is now creating a new Route instance and then passing back the instance for chainable calling. :)

What I still need to work on:

• Converting the $routes array into a class/data-structure of some kind
• More Route class meta (like names and reverse routing?)
• And a more generic add() method in the Klein class for simply adding Route object instances to the Klein routes data-structure without having to go through the respond() method. This allows:
  • Extendable Route classes by using dependency injection
  • Custom Route object definitions external of the respond() method

[Rican7]

Names and reverse routing will be in their own feature branch and PR.
For now, though, this is implemented and closed. :)