Closed weswalla closed 4 months ago
Name | Link |
---|---|
Latest commit | b2186d398e671c8eaf2c6391f1f3776297ca99d1 |
Latest deploy log | https://app.netlify.com/sites/sensemakers/deploys/660b863363c0a20008713f61 |
Deploy Preview | https://deploy-preview-34--sensemakers.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
because of #32 , we can't create a stable access token for testing. Therefore I've instead set up tests that use a valid refresh token and then refresh the access token. The problem with this is that refreshing a token creates a new refresh token and invalidates the old one.
Basically, if we want to have comprehensive testing of a user-wide twitter api client instance, we will probably want our own set of test accounts so that we aren't invalidating the other persons copy of the refresh token.