Conversation
|
Warning Rate limit exceeded@Jordy-Baby has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 36 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. 📒 Files selected for processing (1)
WalkthroughThree new blog posts were added, covering Envio developer updates for April and May 2025 and announcing the winners of the Monad Envio Hackathon. The posts detail recent product releases, new features, blockchain integrations, developer tools, event highlights, and community spotlights. No changes were made to existing exported or public entities. Changes
Possibly related PRs
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 ↗︎
|
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (4)
blog/2025-05-16-monad-hackathon-winners-2025.md (1)
26-26: Typographical refinement
There's an extra space before the closing parenthesis and period in the demo link. Update to:- Watch the [demo](https://www.loom.com/share/b302c11bbd2640ec8b4fc1c85d4cf7c8 ). + Watch the [demo](https://www.loom.com/share/b302c11bbd2640ec8b4fc1c85d4cf7c8).blog/2025-05-28-developer-update-may-2025.md (1)
112-113: Consider a more formal term than 'awesome'
Optionally, replace "awesome" with a more professional adjective (e.g., "insightful", "informative").- Check out the awesome graphs showcasing where traffic is coming from. + Check out the insightful graphs showcasing where traffic is coming from.🧰 Tools
🪛 LanguageTool
[style] ~112-~112: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...(AWESOME)
blog/2025-04-25-developer-update-april-2025.md (2)
62-62: Improve alt text for screenshot
The alt textlogtuiis not descriptive. Consider a more meaningful description, e.g.,Dev console screenshot showcasing indexer progress.
228-228: Correct social links formatting
There's a double pipe||before YouTube. Use a single|to separate links:- [Telegram](...) | [GitHub](...) || [YouTube](...) | [Reddit](...) + [Telegram](...) | [GitHub](...) | [YouTube](...) | [Reddit](...)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (12)
static/blog-assets/dev-update-april-2025-1.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-2.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-3.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-4.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-5.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-6.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-7.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-8.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-9.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-may-2025.pngis excluded by!**/*.pngstatic/blog-assets/monad-hackathon-winners-2025.pngis excluded by!**/*.png
📒 Files selected for processing (3)
blog/2025-04-25-developer-update-april-2025.md(1 hunks)blog/2025-05-16-monad-hackathon-winners-2025.md(1 hunks)blog/2025-05-28-developer-update-may-2025.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
blog/2025-04-25-developer-update-april-2025.md
[style] ~145-~145: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...://github.com/denhampreen/loggregate). Feel free to check out the original background [post...
(FEEL_FREE_TO_STYLE_ME)
[misspelling] ~199-~199: This word is normally spelled as one.
Context: ...oming soon) using Envio, a custom-built multi-chain indexer for Uniswap V3 powered by Hyper...
(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~219-~219: This word is normally spelled as one.
Context: ...# Ship with us. 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...
(EN_COMPOUNDS_MULTI_CHAIN)
blog/2025-05-28-developer-update-may-2025.md
[uncategorized] ~60-~60: Possible missing comma found.
Context: ...k out the walkthrough on Loom or dive into our Loaders gui...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~112-~112: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...
(AWESOME)
[uncategorized] ~143-~143: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...
(COMMA_COMPOUND_SENTENCE_2)
[misspelling] ~173-~173: This word is normally spelled as one.
Context: ...hains. Blazing fast indexing and native multi-chain support make it a game-changer.” - Paul...
(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~189-~189: This word is normally spelled as one.
Context: ...## Ship With Us 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...
(EN_COMPOUNDS_MULTI_CHAIN)
🔇 Additional comments (4)
blog/2025-05-16-monad-hackathon-winners-2025.md (1)
1-5: Frontmatter looks good
The title, sidebar_label, and slug are consistently formatted with other posts.blog/2025-05-28-developer-update-may-2025.md (1)
1-5: Frontmatter looks good
Title, sidebar_label, and slug align with other posts.blog/2025-04-25-developer-update-april-2025.md (2)
1-5: Frontmatter consistency
The title, sidebar_label, and slug are correctly formatted and match repository conventions.
177-178:⚠️ Potential issueFix broken GitHub link
The[GitHub]link is split across two lines, breaking markdown. Combine into one line:- check out his [GitHub](https://github.com/PaulRBerg - ) to stay in the loop! + check out his [GitHub](https://github.com/PaulRBerg) to stay in the loop!Likely an incorrect or invalid review comment.
DZakh
left a comment
There was a problem hiding this comment.
Rabbit left some decent comments.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: Dmitry Zakharov <dzakh.dev@gmail.com>
|
Awesome, Rabbit is pretty cool! Thanks @DZakh :D |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (5)
blog/2025-05-28-developer-update-may-2025.md (5)
19-19: Maintain consistent heading hierarchy
You’ve jumped from##(level 2) to####(level 4) for all subsections. Best practice is to increment one level at a time (e.g., use###for these).Also applies to: 23-23, 38-38, 42-42, 53-53, 62-62, 67-67, 72-72
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
19-19: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4(MD001, heading-increment)
27-36: Specify fenced code block language
Adding a language identifier (e.g., ```javascript` for JS snippets and ```graphql` for the schema example) enables proper syntax highlighting and improves readability.Also applies to: 45-51
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
27-27: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
110-110: Tone down informal language
Consider replacing “awesome” with a more formal term (e.g., “insightful” or “detailed”) to match the professional tone of the post.🧰 Tools
🪛 LanguageTool
[style] ~110-~110: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...(AWESOME)
142-142: Add comma in compound sentence
Insert a comma before “so” to separate the independent clauses:- …open-sourcing their version soon so others can build on it too. + …open-sourcing their version soon, so others can build on it too.
17-17: Unify version-prefix casing
You’ve usedv2.19.0(lowercase “v”) in the “Latest Releases” heading butV2.19.0(uppercase “V”) later on. Please choose one style and apply it consistently.Also applies to: 88-88
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
blog/2025-05-28-developer-update-may-2025.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
blog/2025-05-28-developer-update-may-2025.md
[style] ~110-~110: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...
(AWESOME)
[uncategorized] ~141-~141: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...
(COMMA_COMPOUND_SENTENCE_2)
[misspelling] ~171-~171: This word is normally spelled as one.
Context: ...hains. Blazing fast indexing and native multi-chain support make it a game-changer.” - Paul...
(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~187-~187: This word is normally spelled as one.
Context: ...## Ship With Us 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...
(EN_COMPOUNDS_MULTI_CHAIN)
🪛 markdownlint-cli2 (0.17.2)
blog/2025-05-28-developer-update-may-2025.md
19-19: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
27-27: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
45-45: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🔇 Additional comments (1)
blog/2025-05-28-developer-update-may-2025.md (1)
1-5: Verify required frontmatter fields
Most blog frameworks (e.g., Docusaurus) expect adatefield in frontmatter to properly sort and render posts by publication date. Please confirm whether thedatekey is automatically derived from the filename or needs to be explicitly declared.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
blog/2025-05-28-developer-update-may-2025.md (1)
159-162:⚠️ Potential issueCorrect event name spelling
The event “Pragama” should be spelled “Pragma” to accurately reference Pragma Cannes.- * [Pragama](https://ethglobal.com/events/pragma-cannes) Cannes: July 3rd, 2025 + * [Pragma](https://ethglobal.com/events/pragma-cannes) Cannes: July 3rd, 2025
🧹 Nitpick comments (5)
blog/2025-05-28-developer-update-may-2025.md (5)
27-36: Specify code block language
The fenced code block here lacks a language specifier, which helps with syntax highlighting. Please addjsortypescriptafter the backticks.- ``` + ```js🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
27-27: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
45-50: Add language identifier to code block
The GraphQL schema snippet doesn't specify a language for highlighting. Recommend addinggraphql(orgql) after the opening backticks.- ``` + ```graphql🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
45-45: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
110-110: Consider using a more formal adjective than “awesome”
In professional documentation, “awesome” can come across as casual. Alternatives like “insightful” or “detailed” may better suit the tone.🧰 Tools
🪛 LanguageTool
[style] ~110-~110: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...(AWESOME)
141-141: Add comma before conjunction “so”
These are two independent clauses; inserting a comma before “so” will improve readability.- Even better, they’ll be open-sourcing their version soon so others can build on it too. + Even better, they’ll be open-sourcing their version soon, so others can build on it too.🧰 Tools
🪛 LanguageTool
[uncategorized] ~141-~141: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...(COMMA_COMPOUND_SENTENCE_2)
171-171: Ensure consistent hyphenation of “multichain”
You currently use “multi-chain” in some places. For consistency and alignment with common usage, consider “multichain” (one word) throughout.Also applies to: 186-186
🧰 Tools
🪛 LanguageTool
[misspelling] ~171-~171: This word is normally spelled as one.
Context: ...hains. Blazing fast indexing and native multi-chain support make it a game-changer.” - Paul...(EN_COMPOUNDS_MULTI_CHAIN)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
blog/2025-05-28-developer-update-may-2025.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
blog/2025-05-28-developer-update-may-2025.md
[style] ~110-~110: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...
(AWESOME)
[uncategorized] ~141-~141: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...
(COMMA_COMPOUND_SENTENCE_2)
[misspelling] ~171-~171: This word is normally spelled as one.
Context: ...hains. Blazing fast indexing and native multi-chain support make it a game-changer.” - Paul...
(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~186-~186: This word is normally spelled as one.
Context: ...## Ship With Us 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...
(EN_COMPOUNDS_MULTI_CHAIN)
🪛 markdownlint-cli2 (0.17.2)
blog/2025-05-28-developer-update-may-2025.md
19-19: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
27-27: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
45-45: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🔇 Additional comments (1)
blog/2025-05-28-developer-update-may-2025.md (1)
1-194: Overall, this looks great!
Just a handful of minor markdown and style tweaks above. Once those are applied, this is ready to merge.🧰 Tools
🪛 LanguageTool
[style] ~110-~110: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...(AWESOME)
[uncategorized] ~141-~141: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...(COMMA_COMPOUND_SENTENCE_2)
[misspelling] ~171-~171: This word is normally spelled as one.
Context: ...hains. Blazing fast indexing and native multi-chain support make it a game-changer.” - Paul...(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~186-~186: This word is normally spelled as one.
Context: ...## Ship With Us 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...(EN_COMPOUNDS_MULTI_CHAIN)
🪛 markdownlint-cli2 (0.17.2)
19-19: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4(MD001, heading-increment)
27-27: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
45-45: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
|
Friendly reminder when you get a chance @DZakh 🙏 😄 |
Hey @DZakh - when you get a chance, are you able to assist with a quick review - no need to look over the whole thing as you have already reviewed in Google Docs - just need review to merge, thanks!
Summary by CodeRabbit