It could just be /users/categories/:categoryId

And then the api could add it to current user

Yea!

That’s ideal

So u don’t need userId of the current user in the frontend

If u absolutely do require it, then u can call an API to get the userId of the currently logged in user and then store that in memory

Ahhhh that is interesting, making my brain hurt

Haha.. it is complex. But it’s the right way

I've always done it the other way, but you really dont need to!

Current user is defined by access token All operations are in the context of current user so should operate on current user Unless operation specifically states another user like /users/:userId to show another user

Exactly.

But I should send the User ID with requests like /users though right?

Must be

What is /users?

[ {username: rp, id: 38472-hdakwd-djawd } , { username: Stephano, id: skjdad-3413-akjdha } ]

Response ^

Not sure I understand. Sorry

So if I hit /users endpoint, I get all users and show them on the page

But the API response is that ^

Okay. That’s not an issue

Ahh I see

Also, I’m a little sleepy now (it’s 1:24 am here). So we can chat tomorrow?

Np, I think I understood fully!

Cheers! 👍

Have a good night!

Have a good evening

Does anyone know why I get session expired when the url is incorrect? localhost:4000/users/346c10cd-49d6-43a0-8a12-e22b9515b2fc <- works of course localhost:4000/users//346c10cd-49d6-43a0-8a12-e22b9515b2fc <- throws session expired (notice the //) Video of this: https://imgur.com/cZdnbMV

Is the long string a userId?

Yeah, UUID