-
Notifications
You must be signed in to change notification settings - Fork 11
protocol: make client options configurable #108
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
Conversation
📝 WalkthroughWalkthroughA new JSON file for the Changes
Poem
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
🧹 Outside diff range and nitpick comments (2)
packages/protocol/src/client.ts (2)
49-55: LGTM: Well-structuredCreateClientOptionstype.The new
CreateClientOptionstype is well-defined and includes all necessary options for flexible client configuration. It aligns well with the existing codebase style.Consider adding a brief JSDoc comment to describe the purpose of this type, for improved code documentation:
/** * Options for creating a DNA client. */ export type CreateClientOptions = { // ... existing code };
63-72: LGTM: Correct implementation of new options increateClient.The changes correctly implement the use of the new
CreateClientOptionstype in bothcreateChannelandgrpcCreateClientfunction calls. The use of optional chaining is appropriate.For consistency, consider using optional chaining for all option properties:
const channel = createChannel( streamUrl, options?.credentials, options?.channelOptions ); const client: proto.stream.DnaStreamClient = grpcCreateClient( proto.stream.DnaStreamDefinition, channel, options?.defaultCallOptions );This change makes the code more consistent in how it handles potentially undefined properties.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- change/@apibara-protocol-5cbc4329-6566-4faf-a04d-bdd739e1cca4.json (1 hunks)
- packages/protocol/src/client.ts (2 hunks)
✅ Files skipped from review due to trivial changes (1)
- change/@apibara-protocol-5cbc4329-6566-4faf-a04d-bdd739e1cca4.json
🧰 Additional context used
🔇 Additional comments (3)
packages/protocol/src/client.ts (3)
3-4: LGTM: New imports added correctly.The new imports for
ChannelCredentialsandChannelOptionsare correctly added and necessary for the newCreateClientOptionstype.
61-61: LGTM: ImprovedcreateClientfunction signature.The function signature update simplifies the API by using the new
CreateClientOptionstype. The default empty object foroptionsmaintains backward compatibility, which is a good practice.
Line range hint
1-156: Overall: Well-implemented changes to improve client configuration flexibility.The introduction of the
CreateClientOptionstype and the updates to thecreateClientfunction significantly enhance the API's flexibility and maintainability. The changes are well-implemented and consistent with the existing codebase style. Minor suggestions for documentation and consistency have been provided in the individual comments.
No description provided.