-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Typos in Wiki #21
Comments
Cheers. I've locked the Wiki down for the time being but do plan on opening it up. Just need to get things in order first. Fixed the mistakes. Thanks. 😄 |
Closed
wayne5w
referenced
this issue
Mar 17, 2016
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.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we can't fork the wiki to send pr's, am I correct?
https://github.com/dingo/api/wiki/Internal-Requests
Here it says: Tthe api facade [...]
https://github.com/dingo/api/wiki/Returning-Errors
Here it says under Custom Exceptions:
[...]
return new Response($response, 401);
I think this should be:
return new Dingo\Api\Http\Response($response, 401);
yay?
Cheers
The text was updated successfully, but these errors were encountered: