Access to full response object about twitter-lite HOT 9 CLOSED

I think handling this yourself is the way to go. It's usually very system dependent what you want to do.

from twitter-lite.

This is a huge issue actually. Makes it impossible to build something that requests a larger amount of things without a responsible backoff.

from twitter-lite.

Thanks so much for bringing this up! I'll Add this right now

from twitter-lite.

So would you all prefer managing the rate limiting errors within twitter-lite or just access to the full response object and manage it yourself?

from twitter-lite.

#17 fixes it. I'll have to cut a minor release since the API changes. Thanks for bringing this up!!

from twitter-lite.

@kokarn and @gnomeontherun, if #17 resolves the issue, feel free to close.

BTW, Twitter also has an API endpoint that returns the rate limit status. You can filter for the endpoints that have dangerously low rate limits like this:

async function checkRateLimits() {
  const rateLimits = await twitter.get('application/rate_limit_status', {
   resources: 'friends,statuses,<OTHER_ENDPOINTS_YOU_USE>',
  });
  // Display rate limits for consumed and not fully replenished API endpoints
  for (const resource of Object.values(rateLimits.resources))
    for (const [endpoint, info] of Object.entries(resource))
      if (info.remaining < info.limit / 2)
        console.warn( `WARNING: used 50%+ of the API endpoint limit for ${endpoint}: ${info}`);
});

from twitter-lite.

I haven't got the time right now to look into it in detail, but if the response object is returned that's all that's needed for me.

Good to close from me.

from twitter-lite.

@kokarn: I've found that throwing errors makes handling rate limit responses ([{"message": "Rate limit exceeded", "code": 88}]) much easier. This sentiment has been echoed by twit users as well.

Unless you have a strong objection, I'm going to make this breaking change before we hit 1.0.

from twitter-lite.

This landed in v0.7.0.

from twitter-lite.