I hope noone thinks validation on client-side only is "secure", so good that you address this topic. What drives me crazy, however, is that 1Password popup. 😒
You can also check response.ok which returns a Boolean if response 200-299. This might be better then checking response.status != 200 200-299 errors are successful i.e. created or successful get.
I hope noone thinks validation on client-side only is "secure", so good that you address this topic. What drives me crazy, however, is that 1Password popup. 😒
I know!! I'm trying to find a way to disable it on localhost. Sorry about that!
KING! Keep going James. Ma fav. Thank you!
You can also check response.ok which returns a Boolean if response 200-299.
This might be better then checking response.status != 200
200-299 errors are successful i.e. created or successful get.