In the updated flow of mention-each we have hardcoded the API rate limit to 5. If it gets increased in future we then have to make changes here again. Instead, we can decide the rate limit during runtime by sending out a single message and retrieving the API rate limit from headers.
Expected Behavior
We should decide what the rate limit is during runtime instead of hard coding it. So that in the future if it gets increased, our batch size should also update itself automatically.
Current Behavior
As the batch size is hard coded, it cannot auto-update itself. If the rate limit somehow increases, we need to deploy it again.
Screenshots
Reproducibility
[x] This issue is reproducible
[ ] This issue is not reproducible
Steps to Reproduce
Visit guildRole.ts
Severity/Priority
[ ] Critical
[x] High
[ ] Medium
[ ] Low
Additional Information
Checklist
[x] I have read and followed the project's code of conduct.
[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.
[x] I am willing to contribute to the resolution of this issue.
Issue Description
In the updated flow of
mention-eachwe have hardcoded the API rate limit to 5. If it gets increased in future we then have to make changes here again. Instead, we can decide the rate limit during runtime by sending out a single message and retrieving the API rate limit from headers.Expected Behavior
We should decide what the rate limit is during runtime instead of hard coding it. So that in the future if it gets increased, our batch size should also update itself automatically.
Current Behavior
As the batch size is hard coded, it cannot auto-update itself. If the rate limit somehow increases, we need to deploy it again.
Screenshots
Reproducibility
Steps to Reproduce
guildRole.tsSeverity/Priority
Additional Information
Checklist