chore: fix some function names in comment

[petercover]

fix some function names in comment

Summary by CodeRabbit

• Documentation
  • Updated comment for ordersByMarketDirectionPricePrefix to clarify its purpose in exchange types
  • Corrected comment for GetBlockResults method in tmClient
  • Renamed SignTextWithValidator method to SignTextValidator with updated documentation

[coderabbitai]

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

level=warning msg="[lintersdb] The name "gas" is deprecated. The linter has been renamed to: gosec."
level=warning msg="[lintersdb] The linter named "megacheck" is deprecated. It has been split into: gosimple, staticcheck, unused."

Walkthrough

The pull request encompasses minor documentation updates across three different files. These changes primarily involve renaming methods and updating their corresponding comments to improve clarity and accuracy. The modifications do not introduce any functional changes to the code logic or control flow, focusing solely on enhancing code documentation and method naming conventions.

Changes

File	Change Summary
chain/exchange/types/key.go	Updated comment for ordersByMarketDirectionPricePrefix to clarify its purpose
client/tm/tmclient.go	Corrected comment for GetBlockResults method in tmClient struct
typeddata/typed_data.go	Renamed method from SignTextWithValidator to SignTextValidator and updated its comment

Poem

🐰 Code comments, crisp and bright,
Refactoring with rabbit's might!
Clarity springs from each small tweak,
Making documentation speak
With precision, pure delight! 🔍

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 87a8944 and 7c1d343.

📒 Files selected for processing (3)

• chain/exchange/types/key.go (1 hunks)
• client/tm/tmclient.go (1 hunks)
• typeddata/typed_data.go (1 hunks)

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

• chain/exchange/types/key.go
• client/tm/tmclient.go

🔇 Additional comments (1)

typeddata/typed_data.go (1)

105-106: LGTM! Function name simplified while maintaining clarity.

The function name change from SignTextWithValidator to SignTextValidator and its corresponding comment update improve readability while preserving the semantic meaning.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

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.

[aarmoa]

We don't accept PRs to just change comments into the master branch