Skip to content

chore: set the default value for the options.protocol in the init() of options #3387

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

Merged
merged 2 commits into from
May 27, 2025

Conversation

fukua95
Copy link
Contributor

@fukua95 fukua95 commented May 23, 2025

When the user does not set the protocol option, initConn() sets protocol=3. We can move this behavior of setting the default protocol value to init() of options, so that all default option settings are unified in init().

@fukua95 fukua95 changed the title chore: set the default value for the options.protocol in the init() of options` chore: set the default value for the options.protocol in the init() of options May 23, 2025
…)` of `options`

Signed-off-by: fukua95 <fukua95@gmail.com>
@fukua95 fukua95 force-pushed the chore/option-protocol branch from 0a0215c to b0141f0 Compare May 23, 2025 08:55
@ndyakov
Copy link
Member

ndyakov commented May 23, 2025

@fukua95 would you please update the test case to cover this as well? Also, a short description in the PR body will help us later when we are preparing release notes.

@fukua95
Copy link
Contributor Author

fukua95 commented May 23, 2025

@fukua95 would you please update the test case to cover this as well? Also, a short description in the PR body will help us later when we are preparing release notes.

My bad. I will update it.

Signed-off-by: fukua95 <fukua95@gmail.com>
@ndyakov ndyakov self-requested a review May 27, 2025 11:53
Copy link
Member

@ndyakov ndyakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ndyakov ndyakov merged commit 28a3c97 into redis:master May 27, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants