-
It must make using the API easier...it shouldn't be an abstraction for abstraction sake
-
when you get a session token - can you store it for future sessions? - what mechanism is used to retrieve a new one if the old one fails within the request/response cycle.
-
automatically close session tokens
-
should you hide error codes - or just raise them from the original api? - for example authentication fails on the client api login - I should raise an exception but what kind?
-
Should you catch API access codes and raise your own errors
Last active
July 24, 2019 06:07
-
-
Save surfer190/d3f8d1dff3f82e0e6723b1b1f474f737 to your computer and use it in GitHub Desktop.
API wrapper Concerns
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment