It’s hard when you hit an endpoint that hits another endpoint, because technically the first request IS a 200. No right or wrong way as long as they are consistent and document it clearly imo
It’s hard when you hit an endpoint that hits another endpoint, because technically the first request IS a 200. No right or wrong way as long as they are consistent and document it clearly imo
This is why I write down the questions I’m trying to answer in a text doc, e.g:
Where is this network call comming from? …/some-api-call.js Why do you think it’s causing a 403?
Etc. So if I lose my thought (all the time), I know exactly what and why I was doing it. Also stops you from re-investigating things you forget
No, but that’s not the point. Mobile phones and apps are specifically engineered to draw your attention as much as possible. Children are especially vulnerable to distractions, and so to me it makes sense to serverely limit their usage in the classroom.
Not everything has to be as black and white as “stop”. A step in the right direction is a good one.
Can / should you use it for anything other than IPs?