in reply to Re: Better names for SCRIPT_NAME/PATH_INFO in a web framework?
in thread Better names for SCRIPT_NAME/PATH_INFO in a web framework?

Thank you!

route_name is definitely worth a shot. I'm also thinking about route_path, preparing ground for $request->route->path even though the latter is far, far ahead.

route_param(s) evokes thoughts about the parameters of the route itself, not sure... Although I have a lot of other param's there, so one more won't hurt...

  • Comment on Re^2: Better names for SCRIPT_NAME/PATH_INFO in a web framework?