Skip to content

Conversation

@XanderD99
Copy link
Contributor

Introduces the RX option to SET and FSET commands, enabling clients to request immediate, inline object responses in various formats after mutations. Enhances usability by allowing flexible response types such as object, point, bounds, hash, and support for WITHFIELDS. Updates tests to cover new RX behaviors.

Please do not open a pull request without first filing an issue and/or discussing the feature directly with the project maintainer.

Please ensure you adhere to every item in this list

  • This PR was pre-approved by the project maintainer
  • I have self-reviewed the code
  • I have added all necessary tests

Issue number and link

#790

Introduces the RX option to SET and FSET commands, enabling clients to request immediate, inline object responses in various formats after mutations. Enhances usability by allowing flexible response types such as object, point, bounds, hash, and support for WITHFIELDS. Updates tests to cover new RX behaviors.
@tidwall
Copy link
Owner

tidwall commented Jan 28, 2026

Sorry for the slow response.

Regarding the 'RX' option name. I wondering if naming it to 'GET' would be clearer in general.

SET fleet truck1 POINT GET POINT

@XanderD99
Copy link
Contributor Author

Could we then take it a small step further and name it RETURN? but GET is also fine for me

@tidwall
Copy link
Owner

tidwall commented Jan 30, 2026

Sure. I'm good with RETURN.

Replaces the "RX" argument with "RETURN" in SET and FSET commands
for improved clarity and readability. Updates all relevant logic and
test cases to match the new option, ensuring consistency across the
codebase.
@XanderD99
Copy link
Contributor Author

Refactored to be "RETURN"

@tidwall tidwall merged commit f057090 into tidwall:master Jan 30, 2026
1 check passed
@tidwall
Copy link
Owner

tidwall commented Jan 30, 2026

LGTM. Thanks!

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