Chief
KPCKevin Powell - Community
•Created by Viroz on 12/15/2024 in #back-end
Authentication with separate frontend and backend
you can use
expression-session package6 replies
KPCKevin Powell - Community
•Created by Viroz on 12/15/2024 in #back-end
Authentication with separate frontend and backend
If jwt isn't fitting your use case, what did you else look for?
6 replies
KPCKevin Powell - Community
•Created by Viroz on 12/15/2024 in #back-end
Authentication with separate frontend and backend
so like you need realtime updates?
6 replies
KPCKevin Powell - Community
•Created by Faker on 12/11/2024 in #front-end
Axios vs Fetch
in simple analogy:
Like lets say you have to go to supermarket for buying some grocery for you and your friend.
While going out, your friend "intercepts" or "stops" you for a quick addition of an item to the grocery list.
17 replies
KPCKevin Powell - Community
•Created by Faker on 11/26/2024 in #back-end
Why did we use a .catch() rather than a catch() block while handling errors
I hope you get what I am trying to say
7 replies
KPCKevin Powell - Community
•Created by Faker on 11/26/2024 in #back-end
Why did we use a .catch() rather than a catch() block while handling errors
This is because the function is
async it is always going to return a promise. The reason why you dont handle the Exception inside the method is because you want the error to be handled outside, that is why the .catch is written with function run7 replies
KPCKevin Powell - Community
•Created by Faker on 11/26/2024 in #back-end
Why did we use a .catch() rather than a catch() block while handling errors
If you want to handle errors locally inside the function, then it makes sense to add the catch block with the try. However, if you need some robust way of handling any errors, you are propagating the error outside.
7 replies
KPCKevin Powell - Community
•Created by Faker on 11/26/2024 in #back-end
Why did we use a .catch() rather than a catch() block while handling errors
You pretty much got it right
7 replies