Detecting if a route is called via Dingo

[mrtimp]

Hi All,

Is there a current 'correct way' (in a controller) to determine if a call came in via Dingo or not? The current scenario is there is an API and standard Laravel routes served from the same server and I would like the under specific situations to return more relationships (or less) via specific API calls.

[jasonlewis]

I'm not entirely sure what you mean but you might be able to use Route::
requestTargettingApi(Route::getCurrentRequest());

Calls don't "come in" via the API though. Calls should target the API. Bit
confused about what you're doing.
On 17 Apr 2014 06:24, "Tim Philips" notifications@github.com wrote:

Hi All,

Is there a current 'correct way' (in a controller) to determine if a call
came in via Dingo or not? The current scenario is there is an API and
standard Laravel routes served from the same server and I would like the
under specific situations to return more relationships (or less) via
specific API calls.

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

[mrtimp]

Route::requestTargettingApi(Route::getCurrentRequest()) is exactly what I was after!

Thanks.

[jasonlewis]

No worries! I might it easier to call tonight.
On 17 Apr 2014 09:35, "Tim Philips" notifications@github.com wrote:

Route::requestTargettingApi(Route::getCurrentRequest()) is exactly what I
was after!

Thanks.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8?utm_campaign=website&utm_source=sendgrid.com&utm_medium=email#issuecomment-40665300
.

[jasonlewis]

Pushed a change @mrtimp, you should now just use Route::requestTargettingApi() instead of passing in the request. It will use the current request if you don't pass one in.