If I want to create an API, is creating new API Routes necessary?

If I want to create an API, is creating new API Routes necessary?

What do you think about creating it using if (request()->ajax()) in the web.php routes?! Will there be any problems? I think it may conflict with search engines. What do you think?

By the way, these routes/APIs don’t need any authentication.

It’s so frustrating when you write the same code twice

In reality you can do anything you wish, but having routes and controllers for api and web separates help a lot, because
– Middleware are not the same for them
– Testing is not the same.
– Authentication is not the same.
– The intended use is not the same.
– A api don’t have a front that have clues about it, you need to make a better documentation so users and developers know well what it expect, what it does and what expect as a return.

Right… As I said the main problem is repeating the code in both API and WEB controllers

I’ve made everything OOP, but anyways I’ve got to make an object at least in both of them

….
If (request()->ajax()) Resource…
else view…

Is so neat 😀

The same can be said about MVC, you can do all the logic inside a single file.

you can always extract the logic inside a service..

Remember that even errors should be treated and returned differently.

There is like 100 pro of using separates files, and 1 con (repeating code) that can be fix with something like a service.

AS a bonus i will tell you, that i am working in a system where they put together api and web routes in the same controller and web, and some routes are mixed, so i have to navigate in the system looking for where the info came, jumping from controller to controller, so more often that not i remember the family of those that choice to do it in that way.

You’re right, and of course at the end of the day I’ll need the user to be authenticated.

It it seems it worth to repeat the code in 2 separate classes.

Besides, api prefixe will be removed if I write everything in a single method.

Completely agree. I’m a guilty party that mix my api and web controller in one object

The minimum delay is 10sec

You monster

LoL to be fair my app was an upgrade from Laravel 5 🙂

So api.php dont exists then haha. But even so, there’s still a slight different in putting routes in api.php in terms of authentication. So i still choose to put it in web.php

My only regret is I should have separate the Controllers

I have more than 10 controllers for my web.php routes. Even thinking of making the same thing for API scares me.

You are easy to scare…

I have so many routes that i kinda split them up into multiple files lol

i have to work in a controller with a single method of 500 lines, because they wanted to do the job of several controllers in the same place, it have even internal function.

wow.

Ok as bad as my code was I dont think I can beat that haha

function update(){
function user(){…}
function company(){…}
}

but if you want to beat it, you are in the correct way 😂

No thanks haha

That’s too painful even for me to read….

Yes, i also do that sometimes, i triy to do things like userRoute.php and group them i a logic way.

If there are routes that don’t follow the restfull pattern, or if they are to big in logic, i create a new controller, i rather have a
UserFavoriteController
UserFollowController
UserHistoriesController
than a UserController with many unrelated methods.

I try that everything inside the controller follow rest standar method (edit,update,store,…)

You can also do things like
ControllerUsers
And inside of it put all Users related controllers, you don’t need to put all inside the same controller.

yeah I do that as much as I can too. But sometimes I realize it’s just hard to follow. when it’s not meant to be

I find it harder to do the inverse, just putting userFollowUser() inside the UserController, seems ugly and harder for me to follow.

I’ll just create a FollowUserController

then use store and destroy for follow and unfollow that’s it