Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making custom requests through reaper #59

Open
Venefilyn opened this issue Jan 6, 2020 · 0 comments
Open

Making custom requests through reaper #59

Venefilyn opened this issue Jan 6, 2020 · 0 comments

Comments

@Venefilyn
Copy link

Venefilyn commented Jan 6, 2020

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

maxime915 added a commit to maxime915/graw that referenced this issue Aug 23, 2021
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants