DevComp/fxtwitter-docker
1
0
Fork 0
mirror of https://github.com/CompeyDev/fxtwitter-docker.git synced 2025-04-05 10:30:55 +01:00
Code Issues Projects Releases Packages Wiki Activity

Handle invalid API responses better

Browse source
This commit is contained in:
dangered wolf 2022-07-15 16:36:24 -04:00
parent e7308ed55d
commit f7a4203003
No known key found for this signature in database
GPG key ID: 41E4D37680ED8B58
1 changed files with 12 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
src/fetch.ts
View file

@ -55,15 +55,24 @@ export const fetchUsingGuest = async (status: string): Promise<TimelineBlobParti
/* We pretend to be the Twitter Web App as closely as possible,
so we use twitter.com/i/api/2 instead of api.twitter.com/2 */
const conversation = (await (
await fetch(
let conversation: TimelineBlobPartial;
let apiRequest;
try {
apiRequest = await fetch(
`${Constants.TWITTER_ROOT}/i/api/2/timeline/conversation/${status}.json?${Constants.GUEST_FETCH_PARAMETERS}`,
{
method: 'GET',
headers: headers
}
)
).json()) as TimelineBlobPartial;
conversation = (await apiRequest.json());
} catch(e: any) {
/* We'll usually only hit this if we get an invalid response from Twitter.
It's rare, but it happens */
console.error('Unknown error while fetching conversation from API');
continue;
}
if (
typeof conversation.globalObjects === 'undefined' &&