Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using dingo for internal requests #15

Closed
michaeljhopkins opened this issue Apr 28, 2014 · 2 comments
Closed

Using dingo for internal requests #15

michaeljhopkins opened this issue Apr 28, 2014 · 2 comments

Comments

@michaeljhopkins
Copy link

I currently have the backend API built using Teepluss' Restable package. I am now at the point of development that I need a package to make internal calls with. It looks like dingo can only be used for internal requests if the response is also coming from dingo, am I correct in thinking that?
@jasonlewis
Copy link
Contributor

That's correct yes. Internal requests are tied in with the actual API itself. So the API needs to be built with Dingo. Honestly it's not that hard to do, if you look at Dingo\Api\Dispatcher you can pretty see how it sets up a new request and dispatches it internally.

@michaeljhopkins
Copy link
Author

Solid. While I dont think I want to go back and retrofit a portion of the project that is already done and functional, I fully plan on using this for the next platform! Thanks for open sourcing this!

@xLink xLink mentioned this issue Dec 3, 2014
Closed
@rodrigobendia rodrigobendia mentioned this issue Dec 4, 2014
Closed
@donnigunawan donnigunawan mentioned this issue Jun 1, 2015
Closed
@bfmbrandonjames bfmbrandonjames mentioned this issue Jan 4, 2016
Closed
wayne5w referenced this issue Mar 17, 2016
@jasonlewis
Inject a new router instance into the Laravel adapter.
de7bbb4 
Instead of using the existing Laravel router we will use a new instance. This
should prevent the APIs internal dispatcher from overriding the current route
on the actual Laravel router instance.

There does not seem to be any need for the router instance that is injected
into the adapter to be the actual Laravel router, as the adapter just needs
an instance to dispatch the API-only routes.
@hananfauzi hananfauzi mentioned this issue Mar 29, 2016
Closed
@banandam banandam mentioned this issue Apr 21, 2016
Closed
@tankhit tankhit mentioned this issue May 16, 2016
Closed
@tankhit tankhit mentioned this issue Aug 8, 2016
Closed
@cclep cclep mentioned this issue Aug 30, 2016
Merged
@fico7489 fico7489 mentioned this issue Jan 19, 2017
Closed
@imlewc imlewc mentioned this issue Feb 16, 2017
Closed
@sourabhkum sourabhkum mentioned this issue Aug 10, 2017
Closed
@north9527 north9527 mentioned this issue Sep 4, 2017
Closed
@lear2012 lear2012 mentioned this issue Oct 1, 2017
Closed
@winkull winkull mentioned this issue Oct 27, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jasonlewis @michaeljhopkins