docs: integrated unkey's ratelimiter into my project and wrote a blog post on the same#2347
Conversation
Devansh-Baghel
requested review from
MichaelUnkey,
chronark,
mcstepp and
perkinsjr
as code owners
|
|
@Devansh-Baghel is attempting to deploy a commit to the Unkey Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Rate limit exceeded@chronark has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 6 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 Walkthrough📝 WalkthroughWalkthroughThe pull request introduces two new side quests related to the integration of Unkey for API protection and rate limiting. The first quest focuses on creating a template for building an API using a specific framework, while the second encourages users to document their integration experience in a blog post. Updates include new requirements, a points system for participation, and contributions from users, including a blog post entry by Devansh Baghel. Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thank you for following the naming conventions for pull request titles! 🙏 |
Devansh-Baghel
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
oss.gg/7_create_a_template.md (1)
43-44: LGTM! Consider a minor formatting adjustment for consistency.The new entry for the Deno Unkey Ratelimit Starter by Devansh Baghel is correctly formatted and placed. It adheres to the required structure and provides all necessary information.
For consistency with some of the other entries, consider adding a space after the closing square bracket:
-» 10-October-2024 by Devansh Baghel [Deno Unkey Ratelimit Starter](https://github.com/Devansh-Baghel/deno-unkey-ratelimit-starter) +» 10-October-2024 by Devansh Baghel [Deno Unkey Ratelimit Starter] (https://github.com/Devansh-Baghel/deno-unkey-ratelimit-starter)This is a minor suggestion and doesn't affect the functionality or readability of the document.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- oss.gg/7_create_a_template.md (1 hunks)
- oss.gg/8_use_unkey_blog.md (1 hunks)
🧰 Additional context used
🔇 Additional comments (1)
oss.gg/8_use_unkey_blog.md (1)
23-23: LGTM! Blog post entry updated correctly.The changes align well with the PR objectives. The blog post entry has been properly updated with the correct author name, date, and a link to the blog post. This fulfills the requirements of the side quest.
Let's verify the blog post link:
✅ Verification successful
Blog post link verified successfully.
The blog post at the provided link contains all the necessary information regarding Unkey’s ratelimiter and CodeStash. The verification confirms that the link is correct and relevant.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the blog post link and check its content # Test: Check if the blog post link is accessible and contains relevant content curl -s https://dev.to/devanshbaghel/enhancing-codestash-with-unkeys-ratelimiter-4d8c | grep -iE "unkey|ratelimit|codestash" # Expected output: Multiple matches for the keywords, indicating the blog post is about the correct topicLength of output: 11255
|
Hi @Devansh-Baghel can you point out where this is in your project? I don't see Unkey integrated in the main branch and no mention of it in the stack. It looks like you made a template which is separate from the actual repository. |
|
Hi @perkinsjr sorry the latest commit wasn't pushed yet. Here is the commit in the main branch that adds this, also added in the readme of the project. The template repo that i created was for a separate oss.gg submission which i have now gotten the points awarded for. (issue, pr) but the pr for that is still open. |
|
Hey @chronark Hi, is there anything else I should do or notify someone for this pr? |
|
@Devansh-Baghel james will get to it when he's available |
|
Awarding Devansh-Baghel: 1500 points 🕹️ Well done! Check out your new contribution on oss.gg/Devansh-Baghel |
3 participants
What does this PR do?
Integrated Unkey's ratelimiter into my latest project CodeStash to ratelimit an AI feature.
And then wrote an extensive technical blog on dev.to about the same.
Fixes #2346
Type of change
How should this be tested?
Link to the blog post
Link to the AI feature/ratelimited route, Click the "Explain this" button more than 10 times in 60 seconds to get ratelimited.
Checklist
Required
pnpm buildpnpm fmtconsole.logsgit pull origin mainAppreciated
Summary by CodeRabbit