Modify hopr-allocation-on-gnosis and hopr-on-mainnet slugs

[jeandemeusy]

Update the HOPR Allocation on Gnosis subgraph slug from hopr-allocations-on-gnosis to hopr-allocations---gnosis to (hopefully) get a different subgraph ID than for HOPR on mainnet subgraph.

Update the HOPR on Mainnet subgraph slug from hopr-on-mainnet to hopr--mainnet to (hopefully) get a different subgraph IDs.

Also changes the handler for HOPR transfer on Mainnet for the HOPR on mainnet subgraph to reflect recent changes to the published version of the subgraph.

Summary by CodeRabbit

• New Features

  • Renamed event handler for transfer events to improve clarity.
  • Updated project names for consistency across deployment commands.

• Bug Fixes

  • No functional changes; all core functionalities remain intact despite renaming.

[coderabbitai]

Walkthrough

Walkthrough

The pull request involves several renaming changes across multiple files. The function handleHoprTransfer has been renamed to handleTransfert in the mapping.ts file and its reference updated in the subgraph.yaml configuration. Additionally, the project name in the package.json for both the subgraph-allocations-gnosis and hopr-on-mainnet projects has been changed to reflect a new naming convention. These modifications are primarily cosmetic and do not alter the underlying functionality of the code.

Changes

Files	Change Summary
subgraph/packages/hopr-on-mainnet/src/mapping.ts, subgraph/packages/hopr-on-mainnet/subgraph.yaml	Renamed handleHoprTransfer to handleTransfert. The core functionality remains unchanged.
subgraph/packages/subgraph-allocations-gnosis/package.json, subgraph/packages/hopr-on-mainnet/package.json	Renamed project from "hopr-allocations-on-gnosis" to "hopr-allocations---gnosis" and from "hopr-on-mainnet" to "hopr---mainnet", updating related commands accordingly.

Possibly related PRs

• Indexer logs subgraph #366: The changes in this PR involve renaming functions and updating event handlers related to the Hopr protocol, which aligns with the renaming of the handleHoprTransfer function to handleTransfert in the main PR. Both PRs focus on event handling within the Hopr subgraph.

Suggested labels

status:in-review

Tip

OpenAI O1 model for chat

• We have deployed OpenAI's latest O1 model for chat.
• OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model.
• Please share any feedback with us in the discussions post.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0349190 and 24c3ad9.

Files selected for processing (1)

• subgraph/packages/hopr-on-mainnet/package.json (1 hunks)

Files skipped from review due to trivial changes (1)

• subgraph/packages/hopr-on-mainnet/package.json

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 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.