API::route()

[ryanhungate]

Hey Jason, any chance you wanted to build in support for the route() call vs clunky url patterns? :) I think it would be fantastic to do that, so in your internal API requests, they could be so clean.

[jasonlewis]

You mean route names?
On 23 Apr 2014 07:02, "Ryan Hungate" notifications@github.com wrote:

Hey Jason, any chance you wanted to build in support for the route() call
vs clunky url patterns? :) I think it would be fantastic to do that, so in
your internal API requests, they could be so clean.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12
.

[ryanhungate]

Yeah, access the api route with the name for internal requests
On Apr 22, 2014 6:16 PM, "Jason Lewis" notifications@github.com wrote:

You mean route names?
On 23 Apr 2014 07:02, "Ryan Hungate" notifications@github.com wrote:

Hey Jason, any chance you wanted to build in support for the route()
call
vs clunky url patterns? :) I think it would be fantastic to do that, so
in
your internal API requests, they could be so clean.

Reply to this email directly or view it on GitHub<
https://github.com/dingo/api/issues/12>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-41114943
.

[jasonlewis]

Will look into it.
On 23 Apr 2014 12:17, "Ryan Hungate" notifications@github.com wrote:

Yeah, access the api route with the name for internal requests
On Apr 22, 2014 6:16 PM, "Jason Lewis" notifications@github.com wrote:

You mean route names?
On 23 Apr 2014 07:02, "Ryan Hungate" notifications@github.com wrote:

Hey Jason, any chance you wanted to build in support for the route()
call
vs clunky url patterns? :) I think it would be fantastic to do that, so
in
your internal API requests, they could be so clean.

Reply to this email directly or view it on GitHub<
https://github.com/dingo/api/issues/12>
.

Reply to this email directly or view it on GitHub<
https://github.com/dingo/api/issues/12#issuecomment-41114943>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-41117909
.

[jasonlewis]

Implemented. 😄

[ryanhungate]

Hey Jason, latest push does not find the routes by name? URL::route('bla')??

[jasonlewis]

Any other details you can supply would be great. I'm about to head off for
the night so will investigate in the morning. Cheers!
On 6 May 2014 02:49, "Ryan Hungate" notifications@github.com wrote:

Hey Jason, latest push does not find the routes by name?
URL::route('bla')??

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-42209267
.

[ryanhungate]

Well, basically after you pushed that fix 9 days ago i think it was working, although this is kind of on the side project here... but after defining a route with a

   Route::get('blablabla', array( 'as' => 'bla', 'uses' => 'BlaController@bla' ));

then calling

   URL::route('bla'); 

it throws an error in the URL generator saying that the route is not defined.

[ryanhungate]

Also, it seems as if when running:

   php artisan routes

that the urls are not showing up as well.

[jasonlewis]

Is this to do with the API? What I pushed allows you to run API::route so
you can internally call routes using names.
On 6 May 2014 03:05, "Ryan Hungate" notifications@github.com wrote:

Also, it seems as if when running:

php artisan routes

that the urls are not showing up as well.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-42210944
.

[ryanhungate]

That’s what I’m saying… it is throwing an error now when I try to create a URL the route name ( its for a javascript url in a blade file ). I don’t think I did anything to ruin this functionality, but Ill check.

If your saying that the routes dont get registered as they normally do, I guess I can understand that... but it kinda screws up my workflow with the way I use various urls in the application. I hate defining paths, because I tend to change them as I develop.

On May 5, 2014, at 10:06 AM, Jason Lewis notifications@github.com wrote:

sh

[jasonlewis]

You probably can't use URL::route because these routes are not registered
in the actual route collection. So it should never have worked like that.
It was only meant for internal requests. I think I know what you're talking
about so will look into it in the morning.
On 6 May 2014 03:08, "Ryan Hungate" notifications@github.com wrote:

That’s what I’m saying… it is throwing an error now when I try to create a
URL the route name ( its for a javascript url in a blade file ). I don’t
think I did anything to ruin this functionality, but Ill check.

On May 5, 2014, at 10:06 AM, Jason Lewis notifications@github.com
wrote:

sh

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-42211294
.

[ryanhungate]

Cool man thanks a bunch. For what it's worth, i really like this package... Have a great night man.

[ryanhungate]

If you dont think this is a good idea, scratch what I just asked for... I just think it makes sense that the routes be registered that way. Cleaner while your generating urls in your app with names and array params.

[ryanhungate]

Jason, so i may not be doing something right, but im trying to access a route with :

    \API::route('get.my.route');
    /// in the controller also tried
    $this->api->route('get.my.route');

and its not working. Im getting a Symfony \ Component \ HttpKernel \ Exception \ NotFoundHttpException

But if I access the url in the browser, it works

I traced it and it seems like it finds the correct url by the route name right before queueRequest() is called.