[Improvement suggestion] - Queue articles publication to meet forem rate limiting #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi there, thanks for the kind words an the PR! That said, I'm in the middle of a complete rewrite 😅 ! Nothing I wanted to mention before it was done to avoid pressure but I feel like I've got to disclose it now haha. So I'll put this on hold for now and try to take it into account in the new version directly. |
|
Ok it's totally fine for me! Good luck for your rewrite! |
Where did you find those info? I looked here: https://developers.forem.com/api/v1 But couldn't find it 🤔 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I am a big fan and user of dev-to-git!
My articles repository contains like 20 articles, and it's starting to hit API rate limits when dev-to-git is publishing everything. I have to restart the job multiple times if I want my new articles to be eventually published.
I went through forem's documentation, and it seems like the quotas are:
I think that we could use a small queuing lib designed to stay under the 10calls/30sec rate limit when publishing articles.
-> It would not impact people publishing a small amount of articles that much, and would really help big repositories like mine!
I wrote a bit of code that should fix the issue, WDYT? I am open to suggestions and modifications of course.