-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't use pointer to interface #465
Conversation
WalkthroughThe pull request changes the parameter type of Changes
Tip 🌐 Web search-backed reviews and chat
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (1)
✨ Finishing Touches
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pkg/api/payer/service.go (1)
44-44
: LGTM! Good practice to avoid pointer to interface.The change from
*MetadataApiClientConstructor
toMetadataApiClientConstructor
is a good practice in Go. Since interfaces are already pointer-like types internally (containing both type info and data pointers), adding another level of indirection with a pointer is unnecessary. This change makes the code more idiomatic while maintaining the same functionality.Consider applying the same pattern to other interface parameters in the codebase. For example,
blockchainPublisher blockchain.IBlockchainPublisher
is already following this pattern.Also applies to: 51-51
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
pkg/api/payer/service.go
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Lint-Go
Minor fix. Interfaces can be nil, so there is no need for the extra pointer to interface.
Summary by CodeRabbit