Skip to content

Conversation

@hgh1472
Copy link
Contributor

@hgh1472 hgh1472 commented Oct 4, 2025

I think the parameter name o in ZSetOperations was ambiguous and did not clearly represent its purpose.
This PR renames it to value to improve readability and make its role more explicit.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 4, 2025
@hgh1472 hgh1472 force-pushed the refactor/rename-object-parameter branch from 030b931 to e926c4e Compare October 4, 2025 13:58
@mp911de mp911de added type: documentation A documentation update and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 6, 2025
@mp911de mp911de changed the title Rename Object parameter name. Refine ZSetOperations method argument names Oct 6, 2025
@onobc
Copy link
Contributor

onobc commented Oct 23, 2025

Thank you for the improvement @hgh1472 . Closing in favor of a3de357

@onobc onobc closed this Oct 23, 2025
@onobc onobc added this to the 4.0 GA (2025.1.0) milestone Oct 23, 2025
onobc pushed a commit that referenced this pull request Oct 23, 2025
This commit renames the value parameter in several methods in ZSetOperations to be consistent with the other methods and to make the intent of the parameter more clear.

Original Pull Request: #3227

Signed-off-by: hgh1472 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: documentation A documentation update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants