chore: fix some struct names in comment

[fivecut]

fix some struct names in comment

Summary by CodeRabbit

• Documentation
  • Corrected spelling in comments to accurately reflect type names. No changes to functionality or user experience.

[coderabbitai]

Walkthrough

This update makes minor corrections to comments in two files. In pkg/currency/currency.go, the comment for the PicoDollar type is updated to use the correct capitalization, matching the type name. In pkg/fees/contractRates.go, the comment header for the ContractRatesFetcher type is corrected to match the actual type name. No changes are made to code logic, function signatures, or control flow.

Changes

File(s)	Change Summary
pkg/currency/currency.go	Corrected the spelling of "PicoDollar" in the comment to match the type name.
pkg/fees/contractRates.go	Corrected the comment header for ContractRatesFetcher to match the type name.

Possibly related PRs

• chore: fix some comments #649: Both this PR and the referenced PR focus exclusively on correcting comments to match exact type or function names without changing any code logic or declarations.

Suggested reviewers

• fbac

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (1.64.8)

Error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2
Failed executing command with error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 e015a22 and 9fbf006.

📒 Files selected for processing (2)

• pkg/currency/currency.go (1 hunks)
• pkg/fees/contractRates.go (1 hunks)

🔇 Additional comments (2)

pkg/currency/currency.go (1)

9-9: Comment capitalization fix improves clarity.

The correction from "Picodollar" to "PicoDollar" in the comment accurately reflects the type name and improves documentation consistency.

pkg/fees/contractRates.go (1)

40-40: Comment header now matches type name.

The correction from "ContractsRatesFetcher" to "ContractRatesFetcher" in the comment header ensures consistency and clarity in documentation.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.

[macroscopeapp]

Correct struct name references in comments for PicoDollar and ContractRatesFetcher types

Updates documentation comments to match actual type names in:

• currency.go: Fix PicoDollar type comment
• contractRates.go: Fix ContractRatesFetcher struct comment

📍Where to Start

Start with the PicoDollar type definition in currency.go, followed by the ContractRatesFetcher struct in contractRates.go.

---

Macroscope summarized 9fbf006.

[mkysel]

thank you for your contribution