You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an enhancement, the following endpoitns should return a 5xx status code (I suggest 503) when the twitter api keys are not properly configured.
There are two approaches for this:
The naive implementation could just check for the twitter access keys environmental variables in our code and check if they are empty, raising the 5xx error if so.
A good implementation could be to handle the twitter api errors and check what error tell us if the secret keys were not properly set, and show a better error (not the traceback of the twitter response) explaining why did that happened.
I'd encourage whoever is going to do this to use the later.
The text was updated successfully, but these errors were encountered:
As an enhancement, the following endpoitns should return a 5xx status code (I suggest 503) when the twitter api keys are not properly configured.
There are two approaches for this:
I'd encourage whoever is going to do this to use the later.
The text was updated successfully, but these errors were encountered: