i feel like dynamic param is better and more clear (esp when getting more nested)

If it is a post/put/delete param. I would either pass the ID in the body or use searchparams.

If it's a get method, use search params.

I kinda like to keep all methods in one file "put/post/delete/get/patch" etc.

that kinda works for one level, but if you have things relating back to project (ie add/change post for project), it seems way more confusing then a simple PATCH /api/projects/<id>/post/<id> (ie discord api uses similar thing and its so much simpler to undertand and how things relate to eachother then just params)

It’s a GET param, I handle with one single API a get all or by querying by ID

Dynamic param you mean like I do it?

mb i mean dynmic routes

ye I do dynamic routes, but I don’t know if doing the same for an API would be good

Cuz I use dynamic route params and send them to the API with the method on the first message

tho not sure if it’s best practice

in confused whats wrong with dynamic routes?

unless you want to have a really complex api, dynamic route is kinda the way thats been there for ever (ie post for form action)

like for the API? nothing, tho not sure if it’s good practice

it isn't good practice nor bad practice

it's just one of the ways to use it

hmm ok, i havent made my own api much, but i do like the discord one (i cant imagine that being queried)... and any major company that has official api is like that

i mean it is up to you and if its for yourself of 3rd parties, but with at least dynamic route you have to privide that param, but with query you can forget or so and more things possible to annoy you

Let’s say it’s the basics

I would use dynamic routes if it was an express api, but I prefer to keep all in one file so... I'll use searchparams in Next.js

but dynamic routes is better option IMO

yeah i was going to say for a simple express api it is kinda easier, but with things like nextjs they do the hard work and let you do things in more abstracted way

I only use api routes when I need file upload

Mmmmm so then I will keep my API as it is

/api/projects?project_id=${project_id}

you could

what are your other endpoints

I can't when I am using React hook form

(ie any making use of peoject id?)

ah yeah that is why i stopped using as its kinda pain for me - but i wonder why they abstract it so much but dont let you give your own function)

None

then just use dynamic routes

i mean have a look at the url length and removing repetition
GET /api/projects?project_id=${project_id}
GET /api/projects/${project_id}

the only reason id say use query params is if you want to do bulk like
GET /api/projects?project_id=${project_id_a}&project_id=${project_id_b}

I would send project id's comma seperated

Makes sense, I think I will change it to dynamic routes, and use optional route [[…project_id]] so it ISNT obligatory to pass it, just like I need it to be

if you have 2 params with same name it becoms list, use this info wisely as you can break lots of sites (like my own)

I don’t need to pass many tbh

ohh if that is the case, then you could redirect on base :)

What’s that

Wdym

like on /api/projects you can redirect to whatever the default project_id is

End of the day, everything depends on you

you can use however you want

depending on your needs

Nice

Still doesn’t mean any risk to like security or sum

only a risk to security if you make it :) (ie if you fetch user info, ensure they can access)

tho tbf its prob better to just use query param if its this basic and you can have it omitted (not double fetching for some things)