fix: Contract addresses

[fadeev]

The contracts page fetches addresses dynamically from Github, and earlier today we've moved things around in the protocol contracts repo: zeta-chain/protocol-contracts#449

Summary by CodeRabbit

• Bug Fixes
  • Updated contract address URLs to correctly fetch data from the appropriate endpoints for both testnet and mainnet.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-v2	✅ Ready (Inspect)	Visit Preview	Jan 15, 2025 8:15pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces a modification to the contract address retrieval mechanism in the ContractAddresses.tsx component. The primary change involves updating the URL structure for fetching contract addresses, specifically removing the /v2/data/ path segment and directly accessing the /data/ directory for both testnet and mainnet contract address data.

Changes

File	Change Summary
src/components/Docs/components/ContractAddresses.tsx	Updated URLs for contract address data retrieval, removing /v2/data/ path segment

Technical Observations

While the change appears straightforward, it's worth noting that such URL modifications can have implications for data retrieval and potential versioning strategies. The modification suggests a potential backend restructuring or API endpoint consolidation.

Recommendations for future consideration:

• Ensure comprehensive testing of the new endpoint
• Verify that the data structure remains consistent
• Monitor for any potential breaking changes in data retrieval

The change maintains the existing component logic and data handling mechanisms, focusing solely on the data source endpoint.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0404fe8 and f653183.

📒 Files selected for processing (1)

• src/components/Docs/components/ContractAddresses.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/components/Docs/components/ContractAddresses.tsx

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[gartnera]

I'm assuming the format is compatible.

[Mfigueira]

tACK