chore: export near utils

[leoslr]

Description of the changes

Export near utility methods for more flexibility when making near payments.

Summary by CodeRabbit

• New Features
  • Enhanced payment processing capabilities by adding new utility functions related to Near payments.

These changes improve the interface for users interacting with the payment processor, providing access to additional functionalities.

[coderabbitai]

Walkthrough

The changes include the addition of a new export statement in the packages/payment-processor/src/index.ts file. This modification allows all exports from the utils-near module located in the payment directory to be accessible through the index file, thereby enhancing the module's interface without altering existing exports or import statements.

Changes

File Path	Change Summary
packages/payment-processor/src/index.ts	Added export statement: export * from './payment/utils-near';

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant PaymentProcessor
    participant UtilsNear

    Client->>PaymentProcessor: Import from index.ts
    PaymentProcessor->>UtilsNear: Access utility functions
    UtilsNear-->>PaymentProcessor: Return utility functions
    PaymentProcessor-->>Client: Provide utility functions

Loading

---

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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range comments (1)

packages/payment-processor/src/index.ts (1)

Line range hint 1-32: Consider reorganizing exports for improved maintainability

While the current structure is functional, consider the following suggestions for potential improvements:

1. Group related exports together (e.g., all ERC20-related exports, all Near-related exports, etc.).
2. Consider using a consistent export style throughout the file.
3. Consider moving the utils import and export to be with other similar exports.

These changes could enhance readability and maintainability. However, they are not critical and should be implemented only if they align with your project's coding standards and preferences.

Example of grouped exports:

// ERC20 related exports
export * from './payment/erc20';
export * from './payment/erc20-proxy';
export * from './payment/erc20-fee-proxy';
export * from './payment/erc20-transferable-receivable';

// Near related exports
export * from './payment/near-input-data';
export * from './payment/near-conversion';
export * from './payment/near-fungible';
export * from './payment/near-amount-with-ref';
export * from './payment/utils-near';

// Other exports...

// Utils
export * as utils from './payment/utils';

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between fdaf3ed and 6fdde04.

📒 Files selected for processing (1)

• packages/payment-processor/src/index.ts (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

packages/payment-processor/src/index.ts (1)

29-29: LGTM: New export aligns with PR objectives

The addition of export * from './payment/utils-near'; is consistent with the PR's objective to export utility methods related to near payments. This change enhances the module's interface by making these utilities accessible, providing more flexibility when handling near payments as intended.

To ensure this change doesn't introduce any naming conflicts or unexpected side effects, let's verify the contents of the utils-near module: