Add routescan explorer #1349
Add routescan explorer #1349
Conversation
Adding routescan
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Warning Rate limit exceeded@krofax has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 47 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)
📝 WalkthroughWalkthroughThis pull request updates the documentation for interop devnets by replacing placeholder values in the Explorer fields with actual testnet routescan URLs. Specifically, the "Interop devnet 0" and "Interop devnet 1" entries have been modified from showing "TBA" to providing direct links to their respective testnet explorers. Additionally, a new section titled "Block explorers" has been added, which includes a unified block explorer link for the Interop Devnet. The term "Hackathon" has been removed from the 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
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
pages/stack/interop/tools/devnet.mdx (3)
24-24: Consider improving the explorer link format.For better readability and maintainability, consider using a more descriptive link text instead of repeating the URL:
-| Explorer | [https://420120000.testnet.routescan.io/](https://420120000.testnet.routescan.io/)| +| Explorer | [Routescan Explorer (Devnet 0)](https://420120000.testnet.routescan.io/)|
36-36: Consider improving the explorer link format.For better readability and maintainability, consider using a more descriptive link text instead of repeating the URL:
-| Explorer | [https://420120001.testnet.routescan.io/](https://420120001.testnet.routescan.io/)| +| Explorer | [Routescan Explorer (Devnet 1)](https://420120001.testnet.routescan.io/)|
64-64: Consider using more formal language.The term "revolutionary" is informal and subjective. Consider using more technical and objective language:
-* Write a revolutionary app that uses multiple blockchains within the Superchain +* Build an application that leverages multiple blockchains within the Superchain
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
pages/stack/interop/tools/devnet.mdx(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/stack/interop/tools/devnet.mdx
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Redirect rules - docs-optimism
- GitHub Check: Header rules - docs-optimism
- GitHub Check: Pages changed - docs-optimism
- GitHub Check: pr-workflow
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pages/stack/interop/tools/devnet.mdx (1)
60-64: Add missing punctuation for improved readability.Please add a comma after "chain" in the sentence for better readability.
-If you prefer block explorers per chain please see the above section. +If you prefer block explorers per chain, please see the above section.🧰 Tools
🪛 LanguageTool
[typographical] ~63-~63: It seems that a comma is missing.
Context: ... If you prefer block explorers per chain please see the above section. ## Next steps ...(IF_PLEASE_COMMA)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
pages/stack/interop/tools/devnet.mdx(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/stack/interop/tools/devnet.mdx
🪛 LanguageTool
pages/stack/interop/tools/devnet.mdx
[typographical] ~63-~63: It seems that a comma is missing.
Context: ... If you prefer block explorers per chain please see the above section. ## Next steps ...
(IF_PLEASE_COMMA)
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Redirect rules - docs-optimism
- GitHub Check: Header rules - docs-optimism
- GitHub Check: Pages changed - docs-optimism
- GitHub Check: pr-workflow
🔇 Additional comments (1)
pages/stack/interop/tools/devnet.mdx (1)
24-24: Verify the accessibility of explorer URLs.The explorer URLs are returning 403 Forbidden responses, indicating they are not publicly accessible. Please verify the correct URLs or required access configurations.
#!/bin/bash # Check if the explorer URLs are accessible with browser user agent echo "Checking Devnet 0 explorer..." curl -I -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" https://420120000.testnet.routescan.io/ echo "Checking Devnet 1 explorer..." curl -I -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" https://420120001.testnet.routescan.io/Also applies to: 36-36
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pages/stack/interop/tools/devnet.mdx (1)
60-67: Improve section formatting and add comma.The section needs minor formatting improvements:
Apply these changes:
## Block explorers -A unified block explorer of the Interop Devnet can be found here [https://sid.testnet.routescan.io/](https://sid.testnet.routescan.io/). +A unified block explorer of the Interop Devnet can be found here [https://sid.testnet.routescan.io/](https://sid.testnet.routescan.io/). -Alternatively block explorers per chain can be found below: +Alternatively, block explorers per chain can be found below: 1. Interop devnet 0: [Routescan](https://420120000.testnet.routescan.io/) 2. Interop devnet 1: [Routescan](https://420120001.testnet.routescan.io/)🧰 Tools
🪛 LanguageTool
[uncategorized] ~62-~62: Possible missing comma found.
Context: ...](https://sid.testnet.routescan.io/). Alternatively block explorers per chain can be found ...(AI_HYDRA_LEO_MISSING_COMMA)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
pages/stack/interop/tools.mdx(1 hunks)pages/stack/interop/tools/_meta.json(1 hunks)pages/stack/interop/tools/devnet.mdx(2 hunks)
✅ Files skipped from review due to trivial changes (2)
- pages/stack/interop/tools.mdx
- pages/stack/interop/tools/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/stack/interop/tools/devnet.mdx
🪛 LanguageTool
pages/stack/interop/tools/devnet.mdx
[uncategorized] ~62-~62: Possible missing comma found.
Context: ...](https://sid.testnet.routescan.io/). Alternatively block explorers per chain can be found ...
(AI_HYDRA_LEO_MISSING_COMMA)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - docs-optimism
- GitHub Check: Header rules - docs-optimism
- GitHub Check: Pages changed - docs-optimism
🔇 Additional comments (2)
pages/stack/interop/tools/devnet.mdx (2)
24-24: Verify explorer URLs accessibility.The explorer URLs need verification as previous checks returned 403 errors.
Let's verify the URLs are accessible with proper browser headers:
#!/bin/bash # Check if the explorer URLs are accessible with browser headers USER_AGENT="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" echo "Checking Devnet 0 explorer..." curl -I -H "User-Agent: $USER_AGENT" https://420120000.testnet.routescan.io/ echo "Checking Devnet 1 explorer..." curl -I -H "User-Agent: $USER_AGENT" https://420120001.testnet.routescan.io/Also applies to: 36-36
1-75: Documentation follows style guidelines.The document maintains consistent formatting, proper capitalization, and follows the documentation guidelines.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~15-~15: Possible missing comma found.
Context: ...polia instances that support Superchain interop enabling native ETH and SuperchainERC20...(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~53-~53: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...directly to theOptimismPortaladdress and it will go to the same sender address o...(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~62-~62: Possible missing comma found.
Context: ...](https://sid.testnet.routescan.io/). Alternatively block explorers per chain can be found ...(AI_HYDRA_LEO_MISSING_COMMA)
Adding routescan