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
I couldn't see an easy way to access the reaper instance, since it seems instanced and thrown into Account, Lurker, and Scanner.
I need a way to do API calls on my own with the same rate limiting variables. The endpoints I'm looking for is fetch moderator list, accept moderator invitation, new modmail actions, approve and remove posts.
Since the package seems to focus on streams rather than full a API wrapper, it would be nice to be able to get the reaper instance to stay in line with the rate limiting
The text was updated successfully, but these errors were encountered:
This commit is a refactoring of the types bot, Bot, account, lurker, scanner and reaper (with mockReaper). The goal is to make reaper available outside the package (as turnage#59 requests).
Detailed modifications:
- Renaming "reaper" to "Reaper" to export the interface,
- Exporting methods reap -> Reap,
sow -> Sow, get_sow -> GetSow, rateBlock -> RateBlock,
- Adding RateBlock to the new Reaper interface.
To avoid breaking compatibility only private interface/type were modified, one interface was exported with a new method.
No new tests were added : the exported methods are already tested and no new functionalities were added.
I couldn't see an easy way to access the reaper instance, since it seems instanced and thrown into Account, Lurker, and Scanner.
I need a way to do API calls on my own with the same rate limiting variables. The endpoints I'm looking for is fetch moderator list, accept moderator invitation, new modmail actions, approve and remove posts.
Since the package seems to focus on streams rather than full a API wrapper, it would be nice to be able to get the reaper instance to stay in line with the rate limiting
The text was updated successfully, but these errors were encountered: