Skip to content
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

Rename offensive defines and members in API #140

Merged
merged 4 commits into from
Dec 18, 2024

Conversation

bjosv
Copy link
Collaborator

@bjosv bjosv commented Dec 13, 2024

  • Rename offensive cluster role defines in the API:
    Use VALKEY_ROLE_PRIMARY instead of VALKEY_ROLE_MASTER.
    Use VALKEY_ROLE_REPLICA instead of VALKEY_ROLE_SLAVE.
    Use VALKEY_ROLE_UNKNOWN instead of VALKEY_ROLE_NULL.
  • Rename valkeyClusterNode member slaves to replicas.
  • Rename offensive variables.
  • Improve wording in migration guide (Review comment).

Use primary/replica instead of master/slave and use
unknown instead of null.

Signed-off-by: Björn Svensson <bjorn.a.svensson@est.tech>
Signed-off-by: Björn Svensson <bjorn.a.svensson@est.tech>
Signed-off-by: Björn Svensson <bjorn.a.svensson@est.tech>
Signed-off-by: Björn Svensson <bjorn.a.svensson@est.tech>
@bjosv bjosv requested a review from zuiderkwast December 17, 2024 12:36
Copy link
Collaborator

@zuiderkwast zuiderkwast left a comment

Choose a reason for hiding this comment

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

LGTM

When I saw "use UNKNOWN instead of NULL" in the PR description, I first thought it's about renaming the NULL pointers. (I though what!? Is NULL an offesive word?), but then I realized it's about the unknown role. So maybe formulate this in another way, for example use the full macro names instead of a bare NULL. :)

@bjosv bjosv merged commit ea72f48 into valkey-io:main Dec 18, 2024
43 checks passed
@bjosv bjosv deleted the offensive-words branch December 18, 2024 09:06
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.

3 participants